Migrate application modules from J2EE 1.2 to J2EE 1.3

The Application Assembly Tool (AAT) has an option for migrating J2EE 1.2 application modules to J2EE 1.3. The J2EE 1.2 module is kept intact, with a new 1.3 module created. See also the earconvert tool documentation.

Migrate J2EE 1.2 application modules to which you want to add J2EE 1.3 level Web application (WAR) modules, Resource adapter (RAR) modules, Entity bean (EJB) modules, and application client modules. This tool migrates only the application modules. Migrate J2EE 1.2-level modules inside a J2EE 1.2 application module by other means.

Note: When Entity beans are moved from a J2EE 1.2 module to a J2EE 1.3 module, the EJB container will then apply rules defined in the EJB 2.0 specification to these beans. The EJB 2.0 specification mandates that when a findBy method is called on a bean home (except for findByPrimaryKey), the EJB container must cause other Entity beans enlisted in the same transaction to write out their current state to the persistent store. This is to ensure that the findBy operation is performed on the most current data. Application developers should plan for and be aware of any changes to the application behavior as a result of this rule.

Steps for this task

  1. Start the AAT.

  2. Use it to open the J2EE 1.2 application module you want to migrate.

  3. Click Convert EAR from the file menu.

  4. Save the new J2EE 1.3 application.

What to do next

Assemble zero or more new modules of your choice:

Another option is to proceed directly to assembling a new application module. You can create any new modules that you need, while assembling an application module.