On 8/18/07, Phillip Rhodes <[EMAIL PROTECTED]> wrote: > Phillip Rhodes wrote: > > By default the build puts the templates dir, where the "missing" > > resource lives, in the root of the webapp. Guessing that Velocity > > is trying to load this resource from the classpath, I moved the > > templates dir into WEB-INF/classes, and everything works. > > Urk... that's not quite right. I was looking at a dir I'd been > fiddling with, not the build output. What the build gives is > > $WEBAPPROOT/ > WEB-INF/ > classes > lib > web.xml > ... blah > velocity/ > templates/ > blah > > > But in either case, this doesn't work for me, at least > on this particular install of JBoss, until I restructure it like > this: > > $WEBAPPROOT/ > WEB-INF/ > lib > web.xml > ... blah > classes/ > templates/ > blah... > > Thoughts or suggestions?
Sounds like Velocity's resource loader has problems on JBoss. I guess there is a chance that this "bug" has been fixed in a subsequent Velocity release or could be addressed by a different velocity.properties config for JBoss? Any JBoss users care to speak up? - Dave
