Migrate enterprise bean code.
Parent
Implement EJB 3.x applications
There are no migration issues associated with using EJB 3.x beans. Existing applications continue to run as-is and compile without error. The EJB 3.0 and 3.1 specifications have deprecated the use of EJB 1.1 style entity beans. We are encouraged to start migrating to Java™ Persistence API (JPA) or JDBC as a replacement for entity beans.
What to do next
Develop EJB 3.x applications.
Subtopics
- Migrate enterprise bean code to the supported specification
This product supports the EJB 3.1 specification.
- Adjusting exception handling for EJB wrapped applications migrating from Version 5 to v8.5
Because of a change in the Java APIs for XML based Remote Procedure Call (JAX-RPC) specification, EJB applications that could be wrapped in WebSphere Application Server Version 5.1 cannot be wrapped in v8.5 unless you modify the code to the exception handling of the base EJB application.
Related tasks
Migrate enterprise bean code to the supported specification Adjusting exception handling for EJB wrapped applications migrating from Version 5 to v8.5