Re: [Actionframework-users] bug in VelocityInOutVariable for multiple servlets

[Petr T. <Pet...@pi...>]

 >> It seems that Geir is going to fix the problem for Velocity 1.4, so
 >> if you can live with that your .war-s include velocity-*.jar in
 >> WEB-INF\lib folder, I would let this up to Velocity.
 >
 > How is Geir going to fix a problem due to a static variable in
 > actionservlet source code? I don't see what can be done on the
 > velocity side about the fact that
 > org/actionframework/engines/velocity/VelocityInOutVariable.java has a
 > static variable that instead should reflect per webapp (and per
 > velocity configuration) state.

If org.apache.velocity.servlet.VelocityServlet code changes (as
W.Glass-Husain suggested on velocity-user list), then AS' template
engine servlet would be initialized properly and the static
RuntimeInstance in VelocityInOutVariable no problem. Am I right?

 > What has to happen IMHO is for VelocityInOutVariable stop using any
 > static variables, but use one of its constructor arguments for
 > gaining access to velocity functionality.

I just don't want to make unnecessary changes...

- WebMacro/VelocityInOutVariable is going to be replaced by AS' own
   implementation independent on template engine - for AS 0.96
- multiple webapps using Velocity can co-exist if velocity-*.jars are
   included in WEB-INF\lib folder
- using RuntimeInstance, VelocityEngine etc. would stop AS working
   with Velocity 1.1 (Method.invoke() may solve this problem)

Petr
-- 
[ http://dione.zcu.cz/~toman40 - Pet...@pi... - ICQ=22957959 ]