On 10/13/05, Nathan Bubna <[EMAIL PROTECTED]> wrote: > By the way, if i can take this opportunity to do so, VelocityStruts is > in need of some upgrades for the Struts 1.2 and/or 1.3 series. I've > not been free to use Struts in my paid work and volunteer time has > been scarce, so i'm not up to speed on the newer versions. If anyone > is interested in helping out, that would much appreciated. :)
For Struts 1.3, I wouldn't trying to make the VelocityStruts tools obsolete :) The idea with this 1.3 agenda item * ViewContext - A Commons Chain Context that implements the combined VelocityStruts logical API (same signatures). is to eliminate the need for tags to wander all over the contexts looking for this and that. Instead, it will all be in a single object in request scope. (Which in turn might access other objects in session or application scope.) Accessing Struts components directly would be deprecated, and support removed in a later release. Access through the ViewContext would be cannonical, and tag libs support Struts would need to upgrade. Since VelocityStruts has already solved this problem :), I'd like to adopt and adapt that code so that it is part of the Core framework. The big implementation question would be whether to use several objects, as Velocity Struts does, or just roll them back into one. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
