You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Henning Schmiedehausen (JIRA)" <de...@velocity.apache.org> on 2007/03/08 01:10:32 UTC

[jira] Closed: (VELOCITY-84) Classloader problem limit LogSystem creation

     [ https://issues.apache.org/jira/browse/VELOCITY-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Henning Schmiedehausen closed VELOCITY-84.
------------------------------------------


> Classloader problem limit LogSystem creation
> --------------------------------------------
>
>                 Key: VELOCITY-84
>                 URL: https://issues.apache.org/jira/browse/VELOCITY-84
>             Project: Velocity
>          Issue Type: Bug
>          Components: Engine
>    Affects Versions: 1.2
>         Environment: Operating System: All
> Platform: PC
>            Reporter: Uri Agassi
>
> When you run velocity using external-dir ClassLoader (by putting it in the -
> Djava.ext.dir property in the java command line), you cannot use a class for 
> the LogSystem that is in the regular classpath (a NoClassDefFoundError will be 
> issued).
> This will happen every time that the velocity package is on a ClassLoader that 
> is higher in the hierarchy than the LogSystem class, due to the behaviour of 
> the ClassLoader.
> To resolve this, the Velocity.init should have an overloading with a 
> ClassLoader as parameter, and it should be used in every Class.forName in the 
> code.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org