Fyi. I filed a bug with Velocity as well: https://issues.apache.org/jira/browse/VELOCITY-827
Dawid On Sat, May 26, 2012 at 11:10 PM, Benson Margulies <[email protected]> wrote: > Velocity has a nasty reputation for problems on the classpath. I've > fought with it on CXF. > > However, if I'm right, the immediate problem is trivial to fix. > > In SimpleRelocator, I added this || clause to 'canRelocatePath'. If no > one pipes up with a reason why this would cause a disaster, I'm going > to commit it. > > // Allow for annoying option of an extra / on the front of a > path. See MSHADE-119; comes from > getClass().getResource("/a/b/c.properties"). > return path.startsWith( pathPattern ) || path.startsWith ( "/" > + pathPattern ); > > > > On Sat, May 26, 2012 at 2:05 PM, Dawid Weiss <[email protected]> wrote: >>> That log message, however, is nuts. Searching in classpath and then >>> logging that file path? I'd file that as a bug in Velocity. >> >> It is definitely an bad code pattern -- should be either >> class-relative resource or searched via >> classloader, not class + '/' prefix). I see this from time to time >> though; it'll be hard to rule out in general and will recur from time >> to time I bet. >> >> Dawid >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
