<SNIP> On Wed, 16 Mar 2005 04:59:47 -0000, Niall Pemberton <[EMAIL PROTECTED]> wrote: > ----- 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. </SNIP>
I am not against being able to "rewire" at all. But, if you tie the Action to the ActionForm, this inhibits rather than allowing for "rewiring". <SNIP> > > 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. </SNIP> If you tie Actions and ActionForms together, you essentially have a page-centric idea in mind, I think. I would personally just say "goodbye" at that stage. Page-centric is good for those that are a bit OOP challenged, but other than that there is not a lot going for it that I can see. <SNIP> > > 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. </SNIP> I do hope that if Struts v1.3 begins to tie more than the composable request processor to this Command/Chain business that a fork is allowed in Struts v1.2. Once the problems with the Command/Chain idea begin to cause "hacks" that then enslave the framework to the Command/Chain pattern, things will become frozen rather than fluid, in my opinion. Command/Chain is a nice pattern, but it is getting way too much press: way more than its merits can support, I think. 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]
