PQ49522: EJB WITH 21+ METHODS - IF CHECK THE READ-ONLY BOXES FOR SOME METHODS, OTHER METHODS' READ-ONLY BOXES ARE CHECKED AS WELL


APAR

APAR status
Closed as program error.

Error description
Customer has an EJB with more than 21 methods. After deploying
the EJB in WebSphere, he uses the AdminConsole to edit the
Deployment descriptor for the bean. In the Deployment properties
windows, select the "Transactions" tab to set the Transaction
Attribute for the Remote Interface's methods. When you have more
than 21 methods for the beans, not all the methods are displayed
on the same screen, so you have to use the next buttons to
naviage through all the method. When you check the "Read-Only"
checkboxes for some methods and click the "Set" button. The
checkboxes are propagated to the methods on the other screens
that have same ordinal positions. For example, if you check
the 1st method on the first screen, 2nd method on the second
screen, and 3rd method on the third screen and click "Set"
button and the "OK" button. When come back to the "Deployment
descriptor"/"Transactions" screen, you will see the first
three methods in the first screen are checked, the 2nd and 3rd
methods on the second screen are checked and the 3rd method
on the third screen is checked.
Local fix
Problem summary
Customer has an EJB with more than 21 methods. After deploying
the EJB in WebSphere, he uses the AdminConsole to edit the
Deployment descriptor for the bean. In the Deployment properties
windows, select the "Transactions" tab to set the Transaction
Attribute for the Remote Interface's methods. When you have more
than 21 methods for the beans, not all the methods are displayed
on the same screen, so you have to use the next buttons to
naviage through all the method. When you check the "Read-Only"
checkboxes for some methods and click the "Set" button. The
checkboxes are propagated to the methods on the other screens
that have same ordinal positions. For example, if you check
the 1st method on the first screen, 2nd method on the second
screen, and 3rd method on the third screen and click "Set"
button and the "OK" button. When come back to the "Deployment
descriptor"/"Transactions" screen, you will see the first
three methods in the first screen are checked, the 2nd and 3rd
methods on the second screen are checked and the 3rd method
on the third screen is checked.
Problem conclusion
Code fixed for 3.5 code base.  Scheduled to go into
the next ptf for 3.5 which is slated to be 3.5.5.
Temporary fix
Comments
APAR information
APAR numberPQ49522
Reported component nameWAS STANDARD AI
Reported component ID5648C8300
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2001-06-11
Closed date2001-06-26
Last modified date2001-06-26

APAR is sysrouted FROM one or more of the following:

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


Modules/Macros
EJS
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information
Fixed component nameWAS STANDARD AI
Fixed component ID5648C8300

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ49522
IBM Group: Software Group
Modified date: 2001-06-26