I am experiencing classpath/classload problems when trying to use my own
appender class and jboss EJB server. jboss has its own way of dynamically
creating the classpath during system startup. It dynamically reads all the
jars in a specified directory and adds them to it's classpath. It doesn't
export the classpath to the classpath variable.
The problem is that our homegrown appender is included with all of our other
classes in the jar that is deployed by the server. When log4j attempts to
initialize the appender, it can't find the class even though it is in the
jar file along with all our other beans, etc.
So does this indicate the log4j isn't getting its class loader from the
correct source. Or do we have to go back and re-arrange our package
structure and create two seperate jars. Jboss hates it when you have
duplicate classes in the classpath
log4j.appender.errorSMTP=com.earthcars.log.EarthcarsSMTPAppender
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
