So long as this statement... "...the proposed feature changes nothing for regular Action users, it changes nothing for old DispatchAction users, but it makes things a lot simpler for those who want to switch to event-based paradigm with as little efforts as possible."
...is true, count me +1. As long as I can take an existing app and have it work without modification (or with trivial mods at worst), I can't think of a reason not to do this. Frank -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com AIM: fzammetti Yahoo: fzammetti MSN: [EMAIL PROTECTED] Java Web Parts - http://javawebparts.sourceforge.net Supplying the wheel, so you don't have to reinvent it! On Thu, May 4, 2006 1:53 pm, Michael Jouravlev said: > What we has been brought from the stone ages: > > * Base Action class does not dispatch events > * DispatchAction and its flavors do, but they do not allow a user to > derive an action class from some another user's base action > > What we got now in 1.2.9 and 1.3.1+ : > > * ActionDispatcher resolves the inheritance issue, allowing any action > to dispatch events > * EventActionDispatcher makes dispatching an easy and fun task; it > also allows to separate input phase from render phase, at the same > time it allows to trigger event with links (GET), not only with > buttons (POST). > > What appears to be a logical next step: > > * Stick dispatching features in base Action, thus making all actions > to be dispatch actions. > > Benefits: > > * ActionDispatcher will not be needed. > * Any action will be able to dispatch events. > * This makes a mind shift, making people think more in terms of events > and independent webresources, kind of like .NET's code-behind. > > Minor drawback: > > * only one dispatching behavior can be chosen. Considering all job > done before, we how have best-of-breed EventDispatchAction. Its > features (maybe in some modified manner) should be pushed to base > Action class. For those who rely on old-style DispatchAction or > MappingDispatchAction, they will still be available. > > So, the proposed feature changes nothing for regular Action users, it > changes nothing for old DispatchAction users, but it makes things a > lot simpler for those who want to switch to event-based paradigm with > as little efforts as possible. > > Thoughts? Objections? Suggestions? > > Michael. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
