Network Deployment (Distributed operating systems), v8.0 > Develop and deploying applications > Develop Data access resources > Develop data access applications > Develop data access applications > Benefits of resource references > Requirements for setting data access isolation levels > Access intent service


Custom finder SQL dynamic enhancement

To ensure data integrity for applications using custom finders defined on EJB version 1.1 home interfaces, WAS Version 6.x uses custom finder Structured Query Language (SQL) dynamic enhancement to maintain correct SQL locking semantics.

WAS uses SQL clauses applied to the custom finder SQL statements for those custom finders defined with the Update attribute and certain method-level isolation level settings. These dynamic enhancements are applied only if the backend data store supports these clauses.

This support takes affect at run time when the run time attempts to execute container-managed persistence (CMP) persistence operations associated with the custom finders. To ensure that the SQL dynamic enhancements occur correctly for custom finders defined on an EJB version 1.1 home interface accessing a backend data store that requires the special SQL locking clauses, WAS provides new Java Virtual Machine (JVM) and bean (module) properties. These properties enable you to indicate which custom finders should be enhanced, provided the backend store supports the SQL clauses. For more information about these properties, Custom finder SQL dynamic enhancement properties.

There are several important items to consider when using this functionality:


Related


Custom finder SQL dynamic enhancement properties
Establishing custom finder SQL dynamic enhancement server-wide
Establishing custom finder SQL dynamic enhancement on a set of beans
Establishing custom finder SQL dynamic enhancement for specific custom finders
Disable custom finder SQL dynamic enhancement for custom finders on a specific bean

+

Search Tips   |   Advanced Search