We just discovered a classloader-related problem with Velocity when used
in Tomcat 3.2.2 that seems to have come from the 3.2.2-1 RPM.
I have not verified the problem myself. Before I install the RPM and
dive in, I wanted to check if there are any known issues with this RPM.
The problem is related to classloading - it seems that resources living
in a jar in WEB-INF/lib can't be found via
ClassLoader classLoader = this.getClass().getClassLoader();
result= classLoader.getResourceAsStream( name );
where 'this' is something is an instance of something found only in a
jar in WEB-INF/lib.
When the user switched to 3.2.2 from the tgz distro, all worked fine.
I am going to look into this tonight, so if anyone has any information
that can help or spare me this, I would appreciate it.
Thanks
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
System and Software Consulting
Developing for the web? See http://jakarta.apache.org/velocity/
You have a genius for suggesting things I've come a cropper with!
