OK, as you may have seen, XWork is in the sandbox CVS module. I'd like you all to take a look at it and let me know what you think. The main changes are:
* configuration - the current hack at configuration can be seen in src/etc/example/xwork.xml, but this is _not_ the final form. It is merely to showcase the Configuration interface. * views - views are now a View interface with an execute() method, just like actions. In fact, there is no reason, conceptually, that we could just make the View interface and Action, and then do chaining. But I think this way it keeps things simple while still allowing great flexability. There are tree views currently created: 1) ActionChainView - makes another call to GenericDispatcher, but using the existing ActionContext 2) ServletDispatcherView - creates a RequestDispatcher and forwards() it 3) SerlvetRedirectView - this would be used to replace the Redirect.action. Creating a SwingPanelView would be fairly staight forward as well. Views can be customized in the configuration, so we can make ServletDispatcherView more robust (like whether to include or forward) based on parameters passed in xwork.xml. * All actions are aliases -- this probably won't stay the same, but it's no longer the ActionFactory's job to get the action Class, but instead the configuration. Not sure how good of an idea this is, please give me feedback here. * Actions can be "configured" with parameters. So instead of doing com.blah.Foo!someCommand to dictate that an Action should us ethe command "someCommand", you would pass a parameter mapping of "command" -> "someCommand" in xwork.xml. OK, that's it. -Pat ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
