What does being able to use log4j using the same classpath setup
across application servers have to do with J2EE portability? Show
me that part of the spec.
JBoss just uses log4j, there is no modifications made to it.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
Do you have log4j classes in your extended Log4j.jar? If you do take them
out. JBoss 2.4.4 comes with log4j.jar.
BTW, this has nothing do do with portability or compliance. JBoss just
happens to use log4j as well. You would have the same problem if wl used
log4j too.
> -Original Message-
