> >I thought the URLTag wasn't needed because it just uses > >UrlHelper.buildUrl(), which you can also use from Velocity? > > > > I can use from velocity what is really in the velocity context. So, if > UrlHelper is not in the context, i cant use it. > BUT with the extension of velocity-tools, and particulary the toolbox > manager included in the VelocityView package, you can make any tools > available to the templates. This mechanism is the base for the use of the > struts framework with velocity, where some struts ressources are made > available via the toolbox manager. > Hum, of course the choice of a WebWorkVelocityServlet is understandable for > managing the ww tags, but relying on Velocity Tools is maybe a more stable > choice, or complementary ...
Note: since this is a static method it'd be a bit funky. I really think we need to beef up the velocity support and have items directly in the context. VelocityTools is nice and all, but WebWork should provide a core set no matter what. -Pat ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
