IBM SG24-6320-00 Marine Radio User Manual


 
6320ch_DEV_post_migration.fm Draft Document for Review July 28, 2004 7:33 pm
144 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide
8.2.6 Configuration and code changes for migrated EJBs
EJBs developed in VisualAge for Java V3.5.3 follow the EJB 1.0 specification.
these must be converted to EJB 1.1 specification level.
Since the process of converting involves exporting the EJB code from VisualAge
for Java V3.5.3, importing the EJBs into VisualAge for Java V4.0, exporting from
VisualAge for Java V4.0 and then importing into WebSphere Studio Application
Developer V5.1.1, we recommend that you recreate the EJBs in WebSphere
Studio Application Developer V5.1.1, unless you have a very large number of
EJBs, justifying the cumbersome conversion process.
This section details the steps you must take to complete the migration of your
custom EJBs. This includes the following configuration changes:
Change the access isolation level
Add the WCSecurity role
Change the container transaction type
As well as the following code changes:
Remove serialVersionUID constants
Ensure that ejbCreate returns primary key object
Remove java.rmi.RemoteException from remote methods
Match ejbPostCreate and ejbCreate methods
Remove FinderHelper interface
Regenerating the deploy code
It is assumed that you have already migrated your EJBs to WebSphere Studio
Application Developer V5.1.1 using the process described in 7.5, “Migrating
custom EJBs” on page 118.
Access bean string converters
In VisualAge for Java V3.5.3, you were able to specify string converters for the
fields in the EJB when generating the access bean for the EJB, as shown in
Figure 8-2 on page 145.
A similar step does not exist in the access bean editor in WebSphere Studio
Application Developer V5.1.1. However, the access bean creation engine in
WebSphere Studio Application Developer V5.1.1 does create the string
converters for you, if you make sure that your EJBs are configured to use string
converters.