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. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Todd M" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, February 08, 2002 9:18 AM 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
