>From Ceki Gulcu's official manual:
+ACI-As of version 2.4, JBoss uses log4j for its own logging. Consequently,
your own EJBs and web applications will automatically inherit JBoss' log4j
configuration. More often than not you to keep your application's logs
separate from the Applica-tion Server log. JBoss adopting log4j is a step
backward in some sense. There are a number of possible solutions. The
easiest solution is to modify jboss' log4j configuration file. Assuming all
your classes live under +IBw-com.wombat+IB0- package or in packages under com.wombat
, con-figuring a logger called +IBw-com.wombat+IB0- and setting its level and
additivity will isolate all loggers under it, effectively isolating logging
from your code from that of JBoss. For this approach to work properly your
code should not make use of the loggers that JBoss uses such as those under
+IBw-org.jboss+IB0- or the root logger.+ACI-
----- Original Message -----
From: +ACI-Kevin O'Neill+ACI- +ADw-kevin+AEA-rocketred.com.au+AD4-
To: +ACI-JBoss User+ACI- +ADw-jboss-user+AEA-lists.sourceforge.net+AD4-
Sent: Wednesday, February 12, 2003 2:06 PM
Subject: Re: +AFs-JBoss-user+AF0- JBoss +ACY- Log4J
+AD4- On Thu, 2003-02-13 at 01:27, Anders Engstr+APY-m wrote:
+AD4- +AD4- This question must have been asked a thousand times, but I still haven't
+AD4- +AD4- found a solution to the problem.
+AD4- +AD4-
+AD4- +AD4- We're developing an application that will be deployed on JBoss mostly,
+AD4- +AD4- but other application servers might be used as well (Orion, BEA, OC4J
+AD4- +AD4- etc.) We use log4j to handle logging in the application, and the
+AD4- +AD4- depoyable EAR-file is +ACI-setup+ACI- with its own log4j configuration.
+AD4- +AD4-
+AD4- +AD4- JBoss uses log4j to log system messages and, needless to say, this log4j
+AD4- +AD4- configuration collides with the one in our application.
+AD4- +AD4-
+AD4- +AD4- In other app-servers that does not use log4j internally this is not an
+AD4- +AD4- issue.
+AD4- +AD4-
+AD4- +AD4- We need a standard way to specify the log4j configuration independent of
+AD4- +AD4- the application server we are deploying to. It makes total sense to
+AD4- +AD4- separate the appserver logging from the application's logging.
+AD4- +AD4-
+AD4- +AD4- How are folks handling this situation?
+AD4-
+AD4- Remeber that the conf directory is jsut a part of the class path and the
+AD4- log4j config file in there is a standard log4j xml config file. I
+AD4- usually add my logging information to it.
+AD4-
+AD4- +AD4- //Anders
+AD4- --
+AD4- If you don't test then your code is only a collection of bugs which
+AD4- apparently behave like a working program.
+AD4-
+AD4- Website: http://www.rocketred.com.au/blogs/kevin/
+AD4-
+AD4-
+AD4-
+AD4- -------------------------------------------------------
+AD4- This sf.net email is sponsored by:ThinkGeek
+AD4- Welcome to geek heaven.
+AD4- http://thinkgeek.com/sf
+AD4-
++AF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXw-
+AD4- JBoss-user mailing list
+AD4- JBoss-user+AEA-lists.sourceforge.net
+AD4- https://lists.sourceforge.net/lists/listinfo/jboss-user
+AD4-
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user