On 12/5/05, Preston CRAWFORD <[EMAIL PROTECTED]> wrote:
> So given the current state of Struts it would do
> some good to clarify and simplify the direction Struts is headed. Maybe
> make sure that X version of Struts is component-based, Y version is
> action based, etc.

Again, these two things are not mutually exclusive. The problem is
that people got used to thinking that Struts is a rusty action
framework, that is, front controller, usually stateless, and a lot of
handwork. My feeling is that committers don't want to modify/upgrade
Struts to be something else because most of regular users won't accept
(or merely won't understand) the change. Those who need[ed] the
change, will switch or already have switched to JSF or Tapestry or
Wicket. So now Struts code is out, WebWork is in, it may be cleaner,
it may have better implementation, but it is the same old concept.

Conceptually I don't see WebWork being better or even different from
Struts. Heck, it does not even have a DispatchAction analog, there is
no event model and no events thus no event handlers, still the same
old boring execute() method. A button click can be distinguished, but
instead of dispatching event to an event handler WW2 sets a boolean
value.

Still the same gotcha with checkboxes and reset. Still request-based,
non-stateful. I am pretty sure that stateful actions are possible but
Jason prefers stateless mode and because he is now the main developer
of WW2, his point of view will dominate the minds of regular users.

Validation? Conversion? FreeMarker? All this stuff could be added to
Struts 1.x and there are well-known examples of this already been
done.

A new Mustang has underpinnings from Lincoln LS but what's the point
if it still has solid rear axle? The thing is good only for
straight-line races.

Michael.

P.S. The above rant was based on reading WW docs and faq on
OpenSymphony website, not on actual usage. I woud be happy to be
mistaken.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to