On 10/13/05, Nathan Bubna <[EMAIL PROTECTED]> wrote: > sounds good. but i'm not sure i follow totally... has this been done? > or is it just planned? really, i'm not up to speed on Struts 1.3 at > all.
It's on the list, along with some other items, but I wanted to roll Struts 1.3.0 first, in full subproject mode, before getting off on anything else. > just want to be sure i understand here... are you wanting to bring > Velocity(Tools) integration code over to the Core or merely the code > we use to access Struts resources? > > granted, the two aren't clearly delineated in VelocityStruts, but in > general the integration-ish code is in the actual tool classes and > exists to put a Velocity(Tools) friendly API on Struts resources. the > StrutsUtils class is largely where we access struts resources (and i > believe it originated in code from you. :) Haven't decided on the implementation, but I think the idea is sound. We need to wean people away from this idea that tags/controls should access the contexts directly to obtain framework services. The framework should hand them an API object (or helper or tool), and then the controls should get it form there. Under credit where credit is due, the API object idea was Geir's. He was surprised that we didn't have one already :) So, back in the day, I created a prototype to serve as a reference for the Velocity Struts initiative, which we still have lying around. * http://tinyurl.com/97zbh -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
