"Geir Magnusson Jr." wrote: > Inserting into the request is problematic, as this makes some assumptions.
The new support for modular applications relies on a request-scope object, so this will be the cannonical Struts approach. > What I think would be nice is if there was a map of the data elements in the > servlet scopes, so anyone could write a tool to access what they needed. > You also then don't have to have agreement on what this tool is called, what > the interfaces look like, etc. That's part of what the ContextHelper can do. Someone could just tap into the accessors for the data elements, to get what they needed for their own presentation layer. The end-game would be to turn around and have the tag exensions use this object too. So, it's going to be there whether someone chooses to use it or not. > In Velocity, since we don't have any trouble accessing things that aren't > simple property getter/setter methods, we can access a really rich API, and > therefore would be pleased to avoid a lowest-common-denominator object > provided by the controller. I actually like to think of it as a highest-common-denominator object =:o) -- Ted Husted, Husted dot Com, Fairport NY USA. -- Java Web Development with Struts. -- Tel +1 585 737-3463. -- Web http://www.husted.com/struts/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
