IBM Support

PI67535: INCORRECT EJB REFERENCES GENERATED BY ANNOTATIONS PROCESSING FOR APPLICATION CLIENT JAR FILES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Incorrect EJB references can be generated by annotations
    processing for application client jars.  Annotations
    processing can incorrectly overwrite XML values with values
    from annotations.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Annotations data for EJB references     *
    *                      incorrectly overwrites data in module   *
    *                      deployment descriptors.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Processing of EJB annotations for a module can either
    create new EJB references, or can update EJB references
    already defined in the module deployment descriptor.
    The problem fixed by this APAR is that when an existing EJB
    reference is updated, values obtained from annotations
    overwrite values already present in the deployment descriptor.
    The correct behavior is for the value already present in the
    deployment descriptor to have precedence over values obtained
    from annotations.
    EJB annotations include, for example, @javax.ejb.EJB.
    Modules which process EJB annotations include EJB modules, Web
    modules, and Application Client modules.
    This problem can be detected by reviewing merged deployment
    descriptors of deployed applications.  The merged deployment
    descriptors are found in the server configuration
    "applications" folder, which is present in every cell of the
    configuration.
    A merged descriptor is present only if a module is enabled for
    annotations.  This problem cannot occur in a module which is
    not enabled for annotations.
    For example, for an EJB module, the merged deployment
    descriptor is located in the config/applications folder as
    follows:
    PROFILE_HOME/config/cells/CELL_NAME/applications/
    APPLICATION_NAME.ear/deployments/
    APPLICATION_NAME/EJBJAR.jar/META-INF/
    ejb-jar_merged.xml
    

Problem conclusion

  • Code which merged annotations EJB metadata with XML deployment
    descriptor EJB metadata was updated to prevent annotation
    values from overwriting values initially present in the XML
    metadata.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 9.0.0.1.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI67535

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-08-15

  • Closed date

    2016-08-19

  • Last modified date

    2016-08-19

  • APAR is sysrouted FROM one or more of the following:

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

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
14 October 2021