PQ74423: CMP 1.1. Custom Finders do not honor access intent assigned via AAT in the runtime.

APAR status
Closed as program error.

Error description
CMP 1.1 Custom Finder methods have not supported
the access intent applied via AAT in 4.0x and
in follow on releases. This support fixes this
problem.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server 4.02            *
*                 and higher customers that intend to          *
*                 implement EJB CMP 1.1 custom finder methods  *
*                 and use the update access intent "Update"    *
*                 attribute value provided within the tooling  *
*                 products.                                    *
*                                                              *
*                 This support allows the dynamic addition     *
*                 of the correct SQL "FOR UPDATE" semantic     *
*                 for the SQL to be used when updating the     *
*                 database. Note, if the customer's            *
*                 applications are working as is, this         *
*                 support should not be enabled. Once the      *
*                 APAR is installed, the default is to not     *
*                 implement this automatically. The function   *
*                 must be turned on specifically.              *
****************************************************************
* PROBLEM DESCRIPTION: WebSphere EJB 1.1 CMP custom finder     *
*                      methods do not support the dynamic      *
*                      addition of the SQL provided to the     *
*                      database in general when the "Update"   *
*                      attribute is specified in AAT, ASTK     *
*                      or WSAD.                                *
*                                                              *
*                      With this limitation, developers have   *
*                      often had to implement one custom       *
*                      finder to find beans with custom        *
*                      attributes when the beans were to be    *
*                      loadedfor read only use, and then       *
*                      implement a second custom finder to     *
*                      find beans with the same custom         *
*                      attributes but were intended to be      *
*                      updated vs. readonly within a           *
*                      specific transaction. Finally, the      *
*                      developer would have to develop a       *
*                      different implementation of these       *
*                      two methods for each database they      *
*                      deployed the bean against, as many      *
*                      vendors have slightly different "FOR    *
*                      UPDATE" semantic implementations.       *
****************************************************************
* RECOMMENDATION: Customer's who wish to implement EJB 1.1     *
*                 CMP custom finder methods                    *
*                 that honor the access intent attribute set   *
*                 via the tooling products regardless          *
*                 of the database used, should apply the       *
*                 APARs containing this support.               *
****************************************************************
EJB 1.1 CMP custom finders do not dynamically honor the "FOR
UPDATE" SQL semantics that can be set via AAT, ASTK or WSAD.
Problem conclusion
This APAR now adds the ability for EJB 1.1 CMP custom finders
to support dynamically the update intent specified in the
deployment tooling (ASTK, AAT, WSAD).

This behavior is not enabled by default, and various options
exist to enable the function at the server level, bean type
level, and per bean type method.

In general, this function should not be enabled for
applications already working as designed, as the addition of
the SQL could cause incorrect SQL statements. Only new
development scenarios should utilize this support. The server
and bean level support are system configuration options, and
the method level support is set via a reference in the
deployed module.

The details to implement the solution will be included in the
product documentation in subsequent releases, and for now,
interested parties can either review the particular APAR
readmes containing this support or contact IBM for more
information to implement EJB 1.1 CMP custom finders with the
"Update" access intent.

This support applies only to Option B and Option C style entity
beans, and does not to apply to either Option A or beans
involved in inheritance relationships.
Temporary fix
Temporary fix under test is being worked, so far
things look good.
Comments
APAR information
APAR number PQ74423
Reported component name WAS BASE 5.0
Reported component ID 5630A2201
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-05-21
Closed date 2003-10-24
Last modified date 2003-10-24

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:
PQ75185

Modules/Macros
EJBCONTR          

Fix information

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ74423
IBM Group: Software Group
Modified date: Oct 24, 2003