This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I have been developing web-applications with Struts since June 2004. Is it worthwhile to change for every application to Spring, or is this just another framework besides Struts (and some others)? Or is it specifically meant for some kind of application (working with EJBs or something like that)? If you are an intermediate struts developer: would changing to Spring be very difficult (for me as developer) and time-consuming (changing jsp's, action forms, action classes,... to SpringMVC)
Originally posted by Cheng Wei Lee: If I'm not mistaken, EJBs are a big no-no in Spring. To Spring, EJBs are the culprits that make J2EE applications too heavy-weight.
Spring doesn't really discourage the use of EJBs, in fact, it makes EJBs easier. However, most applications don't need EJBs because they'll only ever run on a single server and they don't need the distributed/remote stuff that EJBs provide.
Also, Spring provides many of the services of an EJB container: i.e. declarative transactions and security (via Acegi Security) and makes it much easier to "test" your code. TestingEJBs is hard out-of-container.