I've opted to move this to the webwork extensions rather than have it part of the webwork core. Although the VelocityServlet will be deprecated, that won't be til Velocity 1.5!

One of the features that's extremely appealing about the velocity tool project is the ability to easily add your own helpers to the velocity context. To that end, I've added a ToolContext (similar to velocity tools ToolboxContext) that allows you to add objects to the velocity context.

Finally, to enable this, I added support for chaining additional VelocityContexts to the end of the WebWorkVelocityContext.

Here's a snippet from webwork.properties


# # Allow user defined VelocityContexts to be chained to the end of # the WebWorkVelocityContext # webwork.velocity.contexts=com.opensymphony.webwork.views.velocity.ToolContext

#
# Allow users to place objects into the VelocityContext.  For example,
# the following snippet would place 3 objects in the VelocityContext;
# $name1, $name2, and $name3 that would be references to instances of
# $classname1, $classname2, and $classname3 respectively.  if
# the classname value is not a class, then the value will resolve to a
#  string.  For example, $name4 would resolve to 'hello world'
#
#webwork.velocity.tool.name1 = classname1
#webwork.velocity.tool.name2 = classname2
#webwork.velocity.tool.name3 = classname3
#webwork.velocity.tool.name4 = hello world

M



-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

Reply via email to