We used the bean framework portion of Spring in a couple applications. It was very nice when the client decided to not use EJB Facades we could very simply (less than 10 minutes) switch the whole app over to a POJO Façade. Granted we wrote the POJO Facades at the time we were developing, and the EJB Facades delegated to the POJO, but it was still an amazing turn around.
Also it was nice to have the façades pack around an instance of the necessary DAO(s) that were automagically instantiated when the façade was instantiated at startup. I haven't dug into the web framework of Spring, but I do not plan on switching to it anyway. The IOC aspects of Spring are enough for me. Larry Meadors wrote: >Without exception, every developer I have talked to personally that >has tried SpringMVC said it was way more complex than struts, and >ended up going back (almost all the way) to struts. > >What I have heard is a killer combination is "Spring-managed Struts". >In this permutation, you use struts with a Spring-based request >processor instead of the default struts one. Then, you get much of the >benefit of using spring (managed beans, IoC, etc...) and continue to >use vanilla struts for the remainder of your application. > >I have been hoping to use this model for the last month or so, but >have been too busy to try it myself. Stupid job. ;-) > >Larry > > > -- Forums, Boards, Blogs and News in RiA <http://www.boardVU.com> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
