[ http://issues.apache.org/jira/browse/VELOCITY-461?page=comments#action_12438198 ] Vladimir Goncharov commented on VELOCITY-461: ---------------------------------------------
I think that custom resource loaders should be loaded in this way as well in case when one particular web app needs to redefine the resource loader. But it helps anyway. Thanks I understand that nothing should be on the app server classpath but sometimes it is beyond control and extra flexibility helps in this case. May it can be maid configurable via the property > Class loading issue > ------------------- > > Key: VELOCITY-461 > URL: http://issues.apache.org/jira/browse/VELOCITY-461 > Project: Velocity > Issue Type: Bug > Affects Versions: 1.4 > Environment: any java env > Reporter: Vladimir Goncharov > Priority: Blocker > Fix For: 1.5 > > > If Velocity.jar is loaded from the WL classpath then it cannot load resources > from the war or ear. This applies to both template resources as well as to > the loader of the resources loaders themselves e.g. custom > ClasspathResourceLoader couldn't be loaded when velocity.jar was loaded from > the WL app claspath and the custom class was loaded from the ear. > In my view all appearances of this.getClass().getClassLoader() should be > replaced by Thred.currentThread.getContextClassLoader() > Thanks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
