I have a real concern that Struts is going to continue to be bloated with what are not Struts, not part of the framework, but what are instead really very useful uses of Struts. DispatchAction and its progeny are just one example of this. I would suggest that such offerings would better be managed in a separate application called something like "Struts Patterns" or "Struts Best Practices". Perhaps such classes could be released as classes and either maintained (or preferrably not) independent of Struts?
I would hope that by the term "bloat" I don't convey that such classes are not wonderful ideas and their authors are stellar citizens. It just seems to me that a framework ought to be maintained as a FRAMEWORK and that allowing USES OF THE FRAMEWORK to become part of the framework is a groundwater mistake. Generally, I think it might be better if the actions package were distributed outside Struts proper.
As a framework, there comes a time when something like Struts is done, and we need to move on to other things except diligent maintainence and creating clever uses. My present predeliction is to save what presently exists, clean it up by jettisoned what is not needed, and to watch for good ideas that might arise in uses. This is just a thought.
There needs to be, I think, a clear separation of Struts patterns or clever uses of Struts and Struts itself. I would suggest that something formal be instituted. Thanks for your ears/eyes on this.
Michael McGrady
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
