Migrating enterprise bean code to the supported specification

Support for the Enterprise JavaBeans™ (EJB) 3.0 specification is added for this product.

Before you begin

There are no migration issues associated with using EJB 3.0 beans. Existing applications continue to run as-is and compile without error.
Note: The EJB 3.0 specification has deprecated the use of EJB 1.1 style entity beans. While using EJB 2.x and earlier modules in the product has not yet been deprecated, you are encouraged to start migrating to Java™ Persistence API (JPA) or JDBC.

About this task

Follow these steps as appropriate for your application deployment.

Procedure

  1. Modify enterprise bean code for changes in the specification.
    • You need to migrate the Version 1.1 beans to Version 2.x beans and redeploy them on the product.
      Note: The EJB Version 2.0 specification mandates that before the EJB container runs a findByMethod query, the state of all enterprise beans enlisted in the current transaction be synchronized with the persistent store. This synchronization is done so that the query is performed against current data. When Version 1.1 beans are reassembled into an EJB 2.x-compliant module, the EJB container synchronizes the state of Version 1.1 beans, as well as that of Version 2.x beans. As a result, you might notice some change in application behavior even though the application code for the Version 1.1 beans has not been changed.
  2. Reassemble and redeploy all modules to incorporate migrated code.



In this information ...


Related concepts

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 3:36:59 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-express-iseries&topic=tejbmigr
File name: tejb_migr.html