Thanks, Joe, See within:
<SNIP> > Jack, I'm not really following you. For me, I simply raised the > issue that there is a standard conditional case in processing a > request for Struts: if the form is valid, then do a few things; if it > is not, do a few other things (well, just one, "SelectInput") So I > guess this is talking about something which belongs in the "standard > plumbing chain." > > I don't see a clear way to apply the Strategy pattern to this > specific question, but maybe I'm just missing something. > > Joe </SNIP> I cannot tell what part of the process you guys are discussing half the time. Pretty much everything on the server side is "processing the request", if that includes "building the response". By the "standard plumbing" I mean the processes that normally happen prior to the processing of a request reaching the Action class, or the stuff that is taken care of by the framework. Are you talking about what happens prior to reaching the Action class or what happens before? I assume you are talking about what happens before, but perhaps I am mistaken? I am trying to be helpful here, as I had great hopes that some sort of chain option for the request processor would make building plugins and making life simpler. As things are, if this is about the plumbing, things seem to be potentially more rather than less coupled. Sorry if this is not helpful, but you all obviously talk with each other often enough to leave a bit out of the conversation which I cannot get the uptake on. 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]
