You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by bu...@apache.org on 2002/06/12 09:45:34 UTC

DO NOT REPLY [Bug 9799] New: - Classloader problem limit LogSystem creation

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9799>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9799

Classloader problem limit LogSystem creation

           Summary: Classloader problem limit LogSystem creation
           Product: Velocity
           Version: 1.2
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Source
        AssignedTo: velocity-dev@jakarta.apache.org
        ReportedBy: uri.agassi@cash-u.com


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.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>