Spring and EJB 3.0 are both reactions, in their own ways, to the complexity of EJB 2.1 and the complaints piled upon it. Both support developing with Plain Old Java Objects (POJOs) and give the framework responsibility for handling transactions, security, persistence, etc. But the two use substantially different approaches. In this article, Michael Yuan puts the two frameworks up against one another to see how they stack up.
rating comment: Very good article, which points out the major differences between
I really like the concept of Spring, which can be used perfectly in small enterprise applications. But I think if you want to scale, you should use a standards-based technology like EJB 3.0.