Choosing an embedded EJB 3.x container to run a Java EE 5 application on Tomcat

Question

I am sorry in advance if my question sounds too general - I do all the preliminary research myself, but nothing replaces real experience ...

My goal is to port the legacy Java EE application (pre-EJB 3.x) to Tomcat with an embedded EJB container. My options currently look like this:

• JBoss Embeddable EJB
• Apache OpenEJB
• OW2 EasyBeans Consortium
• anything else?

I expect to use JMS (with MDB), Session beans (stateful and stateless), JPA, and I am very happy to use JSF with Seam.

Now, given the choices above, are there any advantages to using a particular embedded EJB provider?

Answer 1

- , - , EJB- , .

Apache OpenEJB, , EJB 3.1 .

, , , .

JBoss

• : LGPL
• Java: JDK 5.0
• Tomcat: , server.xml
• Tomcat: 5.0 (?)
• Tomcat: Embedded war
• : JNDI (), JBoss TS, JBoss Messaging, JCA, JNDI, EJB, JPA, TX /, EJB JNDI : Tomcat JNDI Tomcat JNDI; Tomcat JNDI
• : JAR
• :
• : , JBoss, JBoss 5.0, Tomcat
• JMS: , JBoss 5.x. JMS hsqldb-persistence-service.xml,
• XA:
• EJB:
• * : *
• : JMS; ; JBoss JNDI
• :
• EJB 3.1:

Apache OpenEJB 3.1

• : Apache
• * Java: * JDK 5.0 6.0
• Tomcat: , script
• * Tomcat: * Tomcat 6.x 5.5
• * Tomcat: * war file
• * : * EJB 3.0 3.1, JTA, JAX-WS, JMS, J2EE-, JPA, JNDI. OpenEJB , OpenJPA, JPA CMP, ActiveMQ JMS/MDB Apache CXF JAX-WS.
• * JNDI: * JNDI
• * : * EAR (), JAR
• : ActiveMQ JMX mbeans
• * : * , , EJB Apache Geronimo
• * JMS Provider: * ActiveMQ
• * XA: *
• * EJB Timer Services: *
• * : * OpenJPA, Hibernate
• * : * OpenEJB OpenJPA JPA CMP, OpenJPA , JavaAgent .
• * : * , .
• * EJB 3.1: * partial

EasyBeans

• * : * LGPL
• * Java: * JDK 5.0 6.0
• Tomcat:
• * Tomcat: * Tomcat 6.x 5.5
• * Tomcat: * war file
• * : * EJB 3.0, JAX-WS, OSGi.
• JNDI:?
• * : * JAR
• :?
• * : * , , JIRA, EJB JOnAS.
• JMS:?
• XA:?
• * EJB Timer Services: *
• * : * OpenJPA, Hibernate, TopLink, EclipseLink
• :
• * : *
• EJB 3.1: