Hi have you used spring and EJB together in a project? It it's good or not. And how, what you used spring and EJB for? thanks
+2
A:
The Spring manual has a comprehensive chapter on EJB integration:
[...] it is important to note that using Spring does not prevent you from using EJBs. In fact, Spring makes it much easier to access EJBs and implement EJBs and functionality within them. Additionally, using Spring to access services provided by EJBs allows the implementation of those services to later transparently be switched between local EJB, remote EJB, or POJO (plain old Java object) variants, without the client code having to be changed.
The value lies mainly in accessing stateless session beans, since they conform more clesely to Spring's service-oriented model of doing things. You also get some value from stateful session beans and entity beans, but only to a limited degree. EJB2 entity beans are so badly designed that no amount of Spring polishing can hide the nastiness beneath.
The question remains as to why you would want to do this. Spring's own capabilities are at least a match for EJB. The most common reason for mixing the two is if you have an existing codebase that uses EJB, and you need to integrate a Spring application with it. If there's no existing EJB, there isn't really any point, you may as well stick with Spring all the way through.
skaffman
2009-12-26 11:53:50