I work for a big corporate and I'm sure that Spring and/or Hibernate would be unwelcome.
The problem is that everyone else chose to use EJB primarily for it's framework benefits (for the reasons I described in my blog), in a local manner. This should not have happened. Sun and the appserver vendors are partially to blame here for making EJB look like solution to world hunger, and the rest of the blame falls on the overzealous users (myself having been one of them too, hehe). Perhaps the greatest example of mis-use is the EJB expert group caving in to popular demand and making EJB have local interfaces. That just made the problem worse. A better approach would have been to state publically after EJB 1.1 that EJB is meant to be used for building large scale systems with DISTRIBUTED components, and all those who do not need remoting should use a framework like struts and be gone.
Originally posted by Venkat Thiru:
It is good too use spring but EJBs can do better.
I RELEASE YOU! (for now .... ) Feel free to peruse this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton