On Wed, 16 Mar 2005 13:22:05 -0500 (EST), Frank W. Zammetti <[EMAIL PROTECTED]> wrote: > It's those of us that CAN'T upgrade, and maybe won't be able to for a > while, that concerns me. And there are those that simply DON'T want to > upgrade too. If there are those of us willing to keep 1.2 alive and > developing, assuming we do so with forward-compatibility in mind, I can't > see why there wouldn't be support for this. >
I've thought about this to some extent already, focusing on page prep functionality. The 1.3 approach to this adds DTD attributes and allows a chain to do the work. Doing this in 1.2 feels awkward. Use a struts class to respond to a request, then require a commons-chain command to do page prep? Some functionality are better suited for back porting, such as configuration inheritance. Page prep, the way 1.3 implements it, doesn't feel like it. To me, page prep functionality that's forward compatible and still feels like a 1.2 struts solution is still a custom ForwardConfig. Hubert > > -- > Frank W. Zammetti > Founder and Chief Software Architect > Omnytex Technologies > http://www.omnytex.com > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
