Is it possible to configure different container for EJB2 Entities in EAP6

Environment

• JBoss Enterprise Application Platform (EAP) 6.x

Issue

• In EAP4/5 the container can be configured in standardjboss.xml where I can find this in EAP6
• With the jboss.xml deployment descriptor it was possible to select a specific EJB container, how this can be achieved in EAP6

Resolution

With EAP6 it is possible to use EJB2 Entity beans with a standard container. The different container configurations are no longer supported.

If this specific functionality is imperative to your application, contact your Red Hat sales representative regarding the Red Hat Extended Life Cycle support (ELS) as a short gap measure until you can adapt your applications for EAP 6.

To use managed persistence in a future proof way it is recommended to migrate the EJB2 CMP Entities and use JPA (Java Persistence Api) according to the EJB3 specification.

Supported configurations options and known isues with CMP in EAP6:

• Modification Exception JBAS018845 for CMR
• Configurations insert-after-post-create, call-ejb-store-on-clean
• Content from docs.jboss.org is not included.Access to methods without explicit security metadata, on a secured bean

Root Cause

EJB2 and CMP will be an older part of the EJB specification and therefore the support of Entities will be completely removed in further versions of EAP which support Java EE7 as it is _pruned. See Content from download.oracle.com is not included.Java EE7 specification.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.