Hi again, I have added a toolbox.xml - it is loaded OK - however the same symptoms occur, which is, VelocityViewServlet ignores the ResourceLoaders defined in velocity.properties and uses a simple FileResourceLoader instead.
The VelocityServlet instances that are in the same webapp all happily use the ResourceLoaders from the velocity.properties to track down *.vm's, however even though VelocityViewServlet says it is reading the custom velocity.properties it only uses a FileResourceLoader with path "." (I have verified this because to make the VVS work, I have to put the *.vm files it wants in the tomcat bin directory when I run tomcat!! - that way the FileResourceLoader being used by VVS finds the *.vm's... but I don't want to use a FileResourceLoader, I need the *.vm's in the WAR!). I can see the FileResourceLoader being loaded last in velocity.log (and I assume clobbering my WebApp and Classpath resource loaders): 2006-12-14 09:03:45,941 - ResourceLoader instantiated: org.apache.velocity.runtime.resource.loader.FileResourceLoader 2006-12-14 09:03:45,942 - FileResourceLoader : adding path '.' I just don't know where it is coming from and how to kill it - FileResourceLoader is no good when you want a transportable WAR for deploying! Thankyou for your thoughts Velocitites ;-) p.s. it would be I think better if the error message "2006-12-14 09:08:26,800 - ResourceManager : unable to find resource 'aa0006.vm' in any resource loader." specifically listed which ResourceLoaders it had actually tried.... Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
