-----Original Message----- >I looked at Spring 3 briefly and liked what I saw. I didn't dig deep, so I >can't form a real opinion (there is more to a real web app than a hello world >form), but at least the "Spring requires too much configuration" argument is no longer valid. Spring 3 does its part in using convention over configuration, and using annotations instead of XML.
I did notice the same thing. But then I looked closer and noticed that the big difference between Stripes and Spring MVC still is, that Stripes action beans are threat safe and Spring 3 MVC beans are not threat safe. Just like Servlets the Spring MVC beans are singletons with multiple active threats running through them. Unlike Stripes they can't use instance variables. Thus the Spring beans have to use local variables, a programming model that leads to more complex procedural code. ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Stripes-users mailing list Stripes-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/stripes-users
