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-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Todd
> M
> Sent: Friday, February 08, 2002 12:19 PM
> To: [EMAIL PROTECTED]
> Subject: [JBoss-dev] Code Portability Problem: WebLogic to JBoss
>
>
> About a year ago I extended Log4j's Category class.  I've used it
> heavily in in Servlets/EJB's in JRun and WebLogic.  Now the code
> won't port to JBoss because I can't reference the Log4j.jar in
> JBoss 2.4.4.
>
> If I try to modify run.sh to add ../lib/ext/Log4j.jar to
> JBOSS_CLASSPATH it screws up the class loader for JBoss (says it
> can't find org.jboss.logging.log4j.ConsoleAppender).
>
> Is there any way around this?  I wan't to be able to declare it
> in a global classpath (not in each EAR) just like WebLogic and JRun.
>
> This portability problem leaves me wondering whether JBoss is
> really a J2EE compliant container.  Why would they mess around
> with log4j access?  Very frustrating.  Unfortunately, the
> documentation offers no solution.
>
> Please help if you can.
>
> Thanks,
> - Todd
>
> _________________________________________________________
> View thread online: http://main.jboss.org/thread.jsp?forum=66&thread=8085
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to