On Aug 28, 2006, at 2:00 PM, Matthew Jording wrote:
I am doing a quick test to see if I can cram openejb3 into geronimo
1.2 snapshot. As a first test I am porting the GBeans and noticed
that the org.openejb.mdb.DefaultMdbContainerGBean would be missing
both the base container class and a namespace within openEjb3.
Since I assume this is a move because of a new MDB strategy for
EJB3? If this is for lack of JMS provider implementation how close
are you to supporting activemq?
At this point it would take a lot to cram openejb3 into geronimo 1.2
snapshot.
Fundamentally we are still in the process of merging the openejb 2
and openejb 1 codebases here in openejb 3. Dain Sundstrom has done a
few weeks of work openejb 2 (used in geronimo 1.2) and aligning it
with openejb 3, but there is still a few more weeks to go.
The basic areas to tackle are:
1. alignment of the containers
2. alignment of deployment
We've been doing heavy work on the containers for EJB 3 compliance so
aligning the 2 containers to the 3 containers (and vice versa) is a
moving target. We try and sync when the opportunities arise. There
was a big architecture change in openejb 2 for this purpose (i.e.
partial alignment with openejb 3), but I think we've seen all we are
going to see in the Geronimo 1.2 time frame.
However... if you skipped the GBean route all together and used the
OpenEJB/Tomcat integration to cram OpenEJB 3 into Geronimo/Tomcat,
that may work though it would certainly not offer the same
transaction and security integration you get in the OpenEJB 2 and
Geronimo integration.
-David
Thanks
Matthew Jording
