Noel J. Bergman wrote:
Just out of curiousity, why SpringMVC, and not Struts/WebWork and/or JSF?
Because SpringMVC (in its simplest form, which is what I'm proposing) is very close to VelocityServlet -- which is how the current code is written. It is a request-based framework, and its controllers use HttpServletRequest directly, as the current code does. Used in this manner, SpringMVC is more of Servlets++ than a full MVC framework.
Why not JSF? The current presentation layer uses Velocity. Why not WebWork? We want to use the HttpServletRequest directly Why not Struts? I'll let Dave and Allen answer this one -- Sean
