So really, this is just a question of if what was in ActionSupport in 1.x should now be central/core in 2.x. I still have no strong opinion on this :)
-Pat > Let's break this into 2 discussions: > > 1) CommandDriven. > > I want the CommandDriven pattern to be core to Xwork, not just an > implementation detail of ActionSupport like it is in Webwork. I think > it's immensely powerful and useful. It allows you to have one Action > with multiple entry points without having to do a big if-else block to > do this yourself. It lets you have the same Action for the entry to a > form, when you don't want validation or to try to execute code depending > on set values. With the CommandDriven pattern, you define a command name > with an alias you can call it, and this will call doCommandName using > reflection. Once you're doing reflection for an arbitrary method name, > why not make the method name configurable (while still defaulting to the > old doCommandName)? > > 2) Removing the dependence on the Action Interface > > Once you've made it possible to configure methods to execute on the > Action, it's a small leap to make this the default behavior where, if > you give an alias name for your Action in the <action> element, this is > configured as a Command with a method name of "execute" and you use > reflection here, just like anywhere else with commands. At this point, > the Action Interface can be optional (at least, if not gone altogether). > The advantage here is consistency, and not doing things one way if it's > a command and another if it's the default. > > This would STILL be a generic command pattern, just made more flexible. > The benefit of the CommandDriven pattern is great. The benefit of losing > the Action Interface is more subtle, but it really allows for more > flexibility and makes your code less tied to Xwork, and once it becomes > mostly unnecessary, it just seems like an extraneous carryover. ------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
