I think all of these things are already on the Struts Jericho list. The exception being workflow integration. The Struts Workflow is OK, but I personally don't like to use multiple action paths for workflows. Of course, the really cool thing about the Struts Chain is that it makes it very easy to "integrate" packages like this into Struts. Struts becomes less of a framework and more a framework for writing frameworks.
The other minor exception would be "Chained actions" . I doubt that any of us will ever recommend forwarding from one action to another to form a chain of responsibility. But, again, that's something that the Commons Chain can do much better than conventional Struts Actions ever could. Here's my question to you: If you were a member of a development team, and someone handed you a list like this, what would you do first? And, having answered the question, go ahead and do it, and post it here. The thing about open source is this: You don't have to wish -- *you* can make it so. -Ted. On Sun, 21 Mar 2004 00:22:25 -0800, Nadeem Bitar wrote: >> >> Such as? What kinds of innovations are you looking for, and >> specifically what kinds of things are you seeing other frameworks >> use that Struts could benefit from? >> > > I posted this before but here is my struts 2.0 wish list again: > > > * Leverage JSF and JSTL remove struts tags that have similar > functionality. * Support for IoC. * Cleaner interfaces. * Workflow > integration. * Chained actions * Support for portlet(JSR-168) > > > nadeem bitar > > > -------------------------------------------------------------------- > - To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
