On 12/5/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> 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.

We've been wanting to modify/upgrade Struts for a long time. Witness
the 18-month old roadmap. But, while we were waiting to see see how
JSF would shake out, WebWork did the things we wanted to do, pretty
much the same way we would have done them.

If the point of the exercise were to create a product that we could
market and brand, then we wouldn't bother merging with WebWork. We
could just take code and run with it. Then, we could become rivals,
like Microsoft and Sun, and trade volleys of me-too press releases :)

But, the point of the ASF is not to just create and maintain a
codebase. The point is to foster a community around a codebase, so
that the product can be created, maintained, and recreated, year after
year, decade after decade.


> Conceptually I don't see WebWork being better or even different from
> Struts. Heck, it does not even have a DispatchAction analog,

The idea of DispatchActions are built into the kernal, rather than
tacked on, and easy to miss. WebWork calls the idea "Action Aliasing"
and the framework handles multiple entry points elegantly. WebWork
provides solutions to many of our deepest problems, more than I can
iterate in an email post.

As for the rest of it, yes, WebWork is very similar to Struts. If it
weren't, we would not be able to even begin to consider it as a
successor to Struts Action 1.x.. WebWork started as a Struts
revolution, and now we are welcoming the revolution home. This is the
story of the prodigal child, who returned not bankrupt, but with a
caravan. :)


> 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.

The website documentation is sketchy. But that's easy enough to fix. Film at 11.

-Ted.

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

Reply via email to