----- Original Message ----- From: "Dakota Jack" <[EMAIL PROTECTED]> Sent: Wednesday, March 16, 2005 4:22 AM
> 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. I wasn't suggesting that we do it, just make it possible/simple to re-wire struts in that way (for example) or any other way. > Might as well just go to JSF and Shale? Maybe ;-) but I don't think its that radical, still would be request based web framework, rather than page/component based. > 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. I agree, but handling this doesn't have to mean other scenarios can't be easily handled. > 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. You may be right about this. Making life too flexible could be a support nightmare. Anyway I was just throwing an idea into the ring. Its probably too late now anway and on the basis that contributions count and my contribution to Struts 1.3 has been zero, I doubt this will fly. Niall > Jack --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
