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.
What I'd like to avoid introducing to the core is multiple ways to achieve the same goals. If we added the setup actions to Struts 1.2, they would necessarily need to be in Struts 1.3, and in 1.3, there is already a good way to achieve the same goals.
I also fail to see how introducing and immediately using the setup actions is any less bleeding edge than moving to Struts 1.3; are your architects making these decisions really paying so little attention as to say "hm; version number's OK -- go for it!" ?
I promise to answer questions until kingdom come about ways to build the setup action concept as an optional pluggable library for Struts 1.2 and to consider making changes to Struts 1.2 that improve its ability to have a library like this plugged in. It doesn't diminish the usability of the tools any to not have them integrated into the Struts core, and lots of people are out there happily using non-core extensions to Struts 1.2.
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
