|
From: Rod J. <rod...@in...> - 2003-09-20 16:36:54
|
Attention Velocity users: I've just changed the Velocity support to use the VelocityEngine model rather than a Velocity singleton. This is partly to make testing easier (I plan to add some Velocity tests) but also in case there's ever a need to have a different Velocity setup for different controller servlets. As you know, I hate singletons. And the VelocityConfigurer implementation was a bit misleading in that using two in different servlet XML in the same JVM with different config could have produced unexpected results. This should be backward compatible. The VelocityView now looks for a VelocityConfiguration implementation such as VelocityConfigurer in the current application context hierarchy (it can be shared in the root web app context). The name of this bean doesn't matter. Anyway, please check your Velocity applications against the latest in CVS before we release M2 and let me know if there are any problems. Regards, Rod |