Filter
Top Products
Chapter 8. Post-migration steps 145
Draft Document for Review July 28, 2004 7:33 pm 6320ch_DEV_post_migration.fm
Figure 8-2 Adding string converters to an access bean in VisualAge for Java V3.5.3
The access bean configuration data is stored in the file
ibm-ejb-access-bean.xmi, placed in the ejbModule/META-INF folder of the
WebSphereCommerceServerExtensionsData project in WebSphere Studio
Application Developer V5.1.1. A sample file is shown in Example 8-7. Note that
field1 and field2 have set up string converters, whereas field3 does not. As
field1 is already of type java.lang.String, no converters will be added to the
access bean, but as field2 is of type java.lang.Long, string conversion
accessors will be generated.
The access bean for the EJB shown in Example 8-7 will have the following field
accessors:
public java.lang.String getField1()
public void setField1(java.lang.String)
public java.lang.String getField2()
public java.lang.Long getField2InEJBType()
public void setField2(java.lang.String)
public void setField2(java.lang.Long)
public java.sql.Date getField3()
public void getField3(java.sql.Date)
The ibm-ejb-access-bean.xmi file will automatically be configured with the
string converters that have been set up for the EJB’s access bean in VisualAge
for Java V3.5.3 when the EJB 1.1 JAR file is imported into WebSphere Studio
Application Developer. The only time you will need to edit this file manually is if
you choose to recreate your EJBs manually, or if you need to add fields to an
existing access bean and need to add string converters to the accessor methods
for the new field.