WebWork actions are somewhat like Struts Action and ActionForm combined: they can transfer request parameters and can be stateful, like ActionForm, but they also can process input events, like Action.
I created several rather generic action classes, like DialogAction or CRUDAction, and now working on WizardAction. In all cases I need to process events in DispatchAction style, and at the same time I have session-scoped data, which I store in ActionForm. So, sometimes Action classes do nothing more, than just receive input command, and channel it to actual handler in the ActionForm. I think that Struts should have WebWork-style action, which can do both: keep data and process events. What is opinion on that? What is common pattern to introduce new features in Struts? Should I just submit the patch to Bugzilla and encourage people to vote? Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
