IBM Support

PM01051: Incremental Prepare for Deployment does not detect change of sup plier of ejb-ref in other EAR

Fixes are available

Rational Application Developer for WebSphere Software, Version 7.5.5.1
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Using Rational Application Developer 7.5.4, with Incremental dep
    loyment, the client of an EJBRef does not detect if the supplier
     interface has changed, and does not invoke EJBDeploy when runni
    ng Prepare for Deployment (either explicitly of during Publish).
    
    
    Steps to Reproduce:
    
    -2 EJBProjects with one Session Bean each and one method each, e
    xposed to the Remote interface. Tested with EJBClient projects
    associated to the EJBproject. It is important that each EJB Proj
    ect must be in a separate EAR to reproduce the issue.
    
    -Create one ejb-ref from Project2 to Bean1 in Project1 (remote i
    nterface).
    -Call Prepare for deployment on both projects
    -Add one more method and modify one existing method on Bean1
    -Now the Deployment code of Project2 is no longer correct becaus
    e the interface of bean1 has changed (the ejb client deployment
    code does not implement the new and modified methods of Bean1).
    -If you call Prepare for Deployment or publish Project2, the com
    pilation errors are not resolved.
    
    Workarounds:
    
    1- Disable Incremental deployment (Windows preferences Java EE p
    erform
    Incremental Deployment) and call prepare for deployment on Proje
    ct2
    2- delete the deployment code and call prepare for deployment
    
    Basically with Incremental deployment, the client of an EJBRef d
    oes not
    detect that the supplier interface has changed, and does not inv
    oke
    EJBDeploy.
    

Local fix

Problem summary

  • There is no way to detect whether the interfaces of the
    referenced EJB have changed if the EJB is not within the
    same EAR, since there is no one-to-one relationship between
    the referenced and the referencing bean.
    

Problem conclusion

  • A hidden preference is provided to assume that the
    interfaces of the referenced EJB outside of the EAR has
    changed, when Prepare for Deployment is called.
    Fix delivered in Rational Application Developer V7.5.5.1
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM01051

  • Reported component name

    RATL APP DEV WI

  • Reported component ID

    5724J1901

  • Reported release

    754

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-11-11

  • Closed date

    2010-04-01

  • Last modified date

    2010-04-01

  • 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

    RATL APP DEV WI

  • Fixed component ID

    5724J1901

Applicable component levels

  • R754 PSN

       UP



Document information

More support for: Rational Application Developer for WebSphere Software

Software version: 7.5.4

Reference #: PM01051

Modified date: 01 April 2010