Hi Joel, > We are 99% sure we are going to go with Spring MVC. We are still implementing the JPA/Spring based back end, so right now the UI is simply hello world, but it was pretty simple to get at least something put together.
> The other consideration was JSF 2. I've been using JSF at my full time job for about 3 years now and seen some successes and some difficulties with it. While JSF 2 is much, much better than JSF 1.x, for this project the whole component model felt way too heavy, which is why Stripes was such a draw. > I'm anxiously looking forward to your thoughts on the subject, Freddy. Well, if I was not allowed to use Stripes for whatever reason, I would definitely prefer Spring MVC over JSF 2. JSF 1.x is awful, and JSF 2, although not as bad, is still unnecessarily complicated. 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. Cheers, Freddy ------------------------------------------------------------------------------ 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
