Is SpringSource Working On EJB 3.1 Container?
It seems like SpringSource is working on EJB 3.1 implementation. This makes EJB 3 technology even more interesting and proofs its adoption. The Spring framework then would be "Just Another EJB Container On Steroids" (JAEC :-)) - it would make, however, the integration between EJB 3 and Spring easier, than even now. This lowers the entry barrier for EJB 3 as well: the migration to pure Spring environment, in case EJB 3 wouldn't be sufficient for functional, or non-functional requirements, should be not that hard.
This is actually the second EJB-container implemented by SpringSource. Pitchfork can be used right now, I'm already curious about the new one. So EJB 3 became interesting enough to be supported by ... the spring container. EJB 3 could be deployed then on: Glassfish, JBoss, Geronimo, WebLogic/Oracle, WebSphere SAP, and Spring as possible deployment platform.
There is no such annoucement by us (=SpringSource) and I don't see anything in the links in your post that say differently. Can you explain?
Posted by Eberhard Wolff on August 28, 2008 at 06:55 PM CEST #
I just read it here: http://java.dzone.com/articles/ejb-30-and-spring-25#comment-6184
The content of the comment is:
Reza Rahman replied on Wed, 2008/08/27 - 7:12pm
Thank you for an excellent article. As you know, these are some of the same ideas myself and Debu forwarded in the Spring and EJB 3 chapter of EJB 3 in Action. I definitely see excellent integration opportunities for EJB 3 and Spring, just as I see excellent oppotunities for WebBeans/Seam and EJB 3 integration.
Indeed, I am curently working with SpringSource on an EJB 3.1 Lite implementation for the Spring framework/platform that should make such integration even easier (essentially a follow-up to the Spring Pitchfork project intiated by BEA but not followed through).
Posted by Adam Bien on August 28, 2008 at 10:18 PM CEST #
Oh fine. In my opinion it is a good approach that Spring does: Find a way to the JEE/EJB world. Why not? Spring is a exposed framework, it has to work with other frameworks together. So it is okay, to find the way to the EJB world. But I don't think, that Spring wants to rely in any form on EJB :-) Collaboration is good, dependencies aren't so!
Posted by Heiko Scherrer on August 29, 2008 at 12:49 PM CEST #
I wrote a blog entry about this topic:
Posted by Ryan de Laplante on September 12, 2008 at 07:02 AM CEST #