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

Fixes are available

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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSRTLW","label":"Rational Application Developer for WebSphere Software"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.4","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
01 April 2010

Tips

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

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R754 PSN

Document Information

Share your feedback

Need support?