I made a WebappUberspector to allow expressions like:

        #set($session.foo = 'bar') 

for $request, $session and $application, instead of

        #set($junk = $session.setAttribute('foo','bar))

which use the brand new ChainableUberspector mechanism. I'd like to
include it in the trunk and make it the default in the tools
velocity.property file, but since the user may already use a custom
uberspector, the default configuration will be lost.

That is, I'd put in org/apache/velocity/tools/view/velocity.properties
(tools defaults) :

  # Use the WebappUberspector to allow setting of scoped attributes
  runtime.introspector.uberspect = 
o.a.v.util.introspection.UberspectImpl,o.a.v.tools.view.WebappUberspector

but users already using the SecureUberspector in their
velocity.properties won't see any change and will have to update their
config if they want the new syntax to be available.     

Does it seem ok to you?

  Claude




---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to