One approach to building applications that is supported by Struts 1.3+ is to write a commons-chain based application and plug it into Struts, however, that is only one approach while the existing Action class approach still exists and will exist for a very long time. Personally, I favor using either MappingDispatchAction, Struts Flow, or a custom POJO action class ala JSF.
Therefore, Joe's statement is correct. If you never messed with RequestProcessor, the chain-based processor implementation will not affect you. It is kinda confusing, but the chain used for Struts is not the same chain that Ted was talking about, and in fact, I believe we are trying to separate the two to ensure a clean separation between Struts and application logic. Don On Fri, 18 Feb 2005 09:33:16 -0700, Wendy Smoak <[EMAIL PROTECTED]> wrote: > From: "Vic" <[EMAIL PROTECTED]> > > > Or. you can start doing commons-chain now! And then plug it into > > anything. What Ted Husted said on dev list was words to the effect: > > "people should be no longer be writing Struts applications. They should > > be writing commons-chains (CoR) applications. Then just plug it into > > Struts. ". > > Wait... I think it was Joe who said that if we had never cared about the > Struts RequestProcessor up to now, we could ignore 'chain' since it is just > replacing things behind the scenes inside Struts. > > Is this something different? > > -- > Wendy > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
