-
1. Re: Classpath problem with JBoss 3.2.3
spiritualmechanic May 26, 2004 10:33 AM (in response to sporritt)I'm not sure what the official answer is, but in the past we've had to add classes12.jar/zip to the run.sh script so that it's on the system classpath.
-
2. Re: Classpath problem with JBoss 3.2.3
sporritt May 26, 2004 10:54 AM (in response to sporritt)Hi, thanks for the reply - I got it to work by doing that. It's a very strange problem though - my appender class ultimately extends org.apache.lo4j.AppenderSkeleton, which is found in the file log4j-boot.jar, contained in the main lib directory of JBoss. But after I added my jar file to the classpath, JBoss then complained about not being able to find AppenderSkeleton:
15:49:33,906 WARN [ServiceController] Problem creating service jboss.system:type=Log4jService,service=Logging
java.lang.NoClassDefFoundError: org/apache/log4j/AppenderSkeleton
Yet it's in a jar file in the main lib directory, and - even weirder - travelling up the stack trace you find this:
at java.lang.Class.forName(Class.java:141)
at org.apache.log4j.helpers.Loader.loadClass(Loader.java:160)
at org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:164)
What's that class there? org.apache.log4j.helpers.Loader?? But isn't that in the same jar file as the class it's trying to load??!
So I ended up having to add log4j-boot.jar to the classpath in run.bat! It works but something is not right.
Simon