I agree with Niall, this is more appropriate to the dev list...

Niall Pemberton wrote:
 > I don't see how it could be core for Commands, since Command is part
of Commons Chain and not Struts and is an interface anyway,

This was my first thought upon reading this too. I think the interesting question is what 1.3 developers are going to be doing more often: continuing to use some form of Action, or use generic Commands in their place (whether a chain or just an individual Command). I would think the later myself. In that case, I could envision a DispatchCommand that has the capabilities Michael is talking about.

The bottom line though is I think using Commands is a somewhat different paradigm all on its own, and maybe the whole dispatch concept doesn't make as much sense there. I'm not sure I have an opinion either way, I'm just thinking about this for the first time now :)

In any case, as I've said previously, I don't really see that big a problem with this... I think it would actually be great if we could some day have a single Action class that could do it all. I'm not sure that's feasible, or even a good idea ultimately, but it's a thought. If as Michael proposed, this can be done without affecting existing code (i.e., if I extend UberAction instead of Action, it'll work the same, even though I'm not using dispatch functionality), then that seems like a reasonable idea to me. I'd want to see it before I checked off the "cool with me" box though :)

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!

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

Reply via email to