Probably something like this (I am not positive that this is correct): Since log4j.jar was in your jre dir it was part of boot classloader but your jdbc jar was part of the normal classloader so the log4j classes couldn't see the classes in the normal classloader.
Someone please correct me. On 6/7/05, Andreas Fester <[EMAIL PROTECTED]> wrote: > Hi, > > just to be curious: how can the existence of a user specific > jar file (i.e. other than rt.jar, tools.jar etc.) within some > jre directory influence class loading behaviour, without > being present in some CLASSPATH, -cp or -Xbootclasspath??? > > Any hint welcome :-) > > Thanks and best Regards, > > Andreas > > > Raoul OPPLIGER wrote: > > THE PROBLEM IS RESOLVED. > > > > In fact, it is really a classloader issue. > > I've had an old version of log4j.jar in my jre directory. > > > > If I delete this old version and if I specify the path of jar files in > > the command line, the previous problem is resolved. > [...] > > -- > Andreas Fester > mailto:[EMAIL PROTECTED] > WWW: http://littletux.homelinux.org > ICQ: 326674288 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- James Stauffer Are you good? Take the test at http://www.livingwaters.com/good/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
