OpenEJB is making useful progress
I have been reported by David Blevins that OpenEJB was making useful progress (and hence, Geronimo is making progress too).
My main complain regarding the funky JNDI issues in remote EJB invocation is apparently going away as you can now customize how OpenEJB assigns JNDI names. They also document how they are named by default: something that was greatly missing in the previous releases 
The full annotations support in the Tomcat servlets container is now there (I didn’t know it wasn’t working since I had tested Geronimo with Jetty as a Servlets container).
He also mentions the fact that OpenEJB provides some unit testing support with a dedicated embedded testing container. Last but not least:
“And in case you’re really at home in GlassFish, we do support their deployment descriptors so you could use OpenEJB for unit testing and still deploy your app into GlassFish.”
Great jobs guys! Glassfish is astonishing, but it needs some fierce competition 
Hints for the Geronimo developers:
- add domains / instances
- drastically improve the startup time.
Good luck!
September 24th, 2007 at 9:22 pm
Thanks for the post! Just to clarify, the Geronimo/Tomcat integration was fully complete and certified (annotations and all) back in June.
The OpenEJB/Tomcat integration I’m referring to is using OpenEJB as a plugin to make a plain Tomcat server capable of handling Servlets with annotations, Transactions, J2EE connectors, JPA Persistence Units, JMS, JavaMail as well as EJB 3.0 support. Plain EAR support will be added, but currently the idea is a little different than standard JavaEE packaging and is all based on our Collapsed EAR concept. Something we hope to get into the JavaEE 6 specifications.