The idea, I thought, was to use the Commands to supplant the RequestProcessor with a composable request processor. Some of the present suggestions are so radical as to provide some question whether Struts is going to be Struts. This is especially so of the suggestion that we tie the ActionForm and the Action together. Might as well just go to JSF and Shale?
If anything, I would tie the ActionForm and the Action less together. I don't care what you call an Action. I do care if it handles the request and returns an ActionForward. If you loose that, you loose Struts altogether in my opinion. The whole command structure, remember, is only because you adapted the Template Method pattern for the parts of the composable request processor requiring the Command/Chain pattern to fix its difficulties. To decide for that reason that the Command/Chain structure is some pattern Valhalla is a serious error, in my opinion. Jack -- "You can lead a horse to water but you cannot make it float on its back." ~Dakota Jack~ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
