Re: [Springframework-developer] Struts (and Re: ErrorCoded/MessageSource)

[<jue...@we...>]

> I agree, there's lots of stuff there, and things we can learn
> from. However, wrt the dispatch action, our=20
> com.interface21.web.servlet.mvc.multiaction.MultiActionControl
> ler does the same thing but is much more powerful.

I'm perfectly aware, of course :-)

What I meant regarding dispatch actions was that Struts 1.1 allows for =
form handling within dispatch actions, i.e. "someAction(request, =
response, form)"-like method signatures. We currently only support the =
"someAction(request, response)"-style, accompanied by =
"someHandler(request, response, exception)-style exception handlers. The =
drawback of Struts 1.1 is that it actually enforces form handling with =
dispatch actions, just like it generally treats every request as a form.

I rather look at Struts in terms of different approaches. For example, =
we don't really need "modules", as we support multiple =
ControllerServlets anyway, which I consider significantly clearer and =
more flexible. It's just that there might be some special functionality =
in Struts that Spring can't provide currently, even if the basic issue =
is addressed.

On the other hand, no new feature should sacrify Spring's clear =
architecture, just for the sake of convenience. We should try to find a =
balance in that respect.

Juergen