RE: [Springframework-developer] MVC DispatcherSevlet vs HandlerServlet

[Alef A. <al...@jt...>]

>>=20
You do have a point there regarding MVC vs servlet support separation.
However, that would only work with a restructing of the package
hierarchy there, because the current "web.servlet" package is
essentially the direct basis for the controllers and views of the MVC
framework. If we wanted to separate those into different modules, we'd
get a problem, because we'd need to separate classes in the same
subpackage tree there.
=20
The current line drawn between spring-web.jar and spring-webmvc.jar is
that the latter includes "web.servlet" plus subpackages and the former
includes everything else. That works pretty well in general, because
spring-web.jar is all you need to make a Spring application context work
with Struts, JSF, Tapestry, any third-party MVC framework.
=20
Of course, once you want to export HTTP-based remote services, you do
need spring-webmvc.jar even when working with a third-party web MVC
framework. I consider that acceptable, though: spring-webmvc.jar simply
includes a generic dispatcher necessary for HTTP-based remoting, which
will coexist nicely with any third-party MVC framework.=20
>>
=20
Well, that's the point :). I personally don't consider including the
webmvc.jar to be a real issue but some people out there (and Jason isn't
the only one :) do! And it results in people creating custom code, which
I don't like :). Let's leave it like it is for now.