On 12/18/05, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > On bugs 33202 and 33996 there is a proposal to remove ChainAction and > DispatchChainAction. If we're going to do it before 1.3, now is the > time. > > http://issues.apache.org/bugzilla/show_bug.cgi?id=33202 > http://issues.apache.org/bugzilla/show_bug.cgi?id=33996 > > I started a trivial example app to try out different ways of executing > commands from Struts, and there are _plenty_ of them just using > <action> in struts-config. > > Martin, since you said you're actually using these classes, do you > want them to stay? Any other opinions?
We're using ChainAction (I'm not a fan of Dispatch* ;) with Struts 1.2.8, where we don't have the luxury of the parameter mechanism for mapping actions to commands. While having this available in 1.3.x would slightly ease migration for us, it never was a released class (it's in the sandbox in 1.2.x), so removing it now, so that it never becomes part of a release, makes sense to me. -- Martin Cooper If we're keeping them, then we need to introduce constants for the > "forward" and "exception" strings under which they expect to find > things in the context. I was about to do that before I discovered > that Joe wanted to remove them entirely. > > Thanks, > -- > Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
