This question must have been asked a thousand times, but I still haven't found a solution to the problem.
We're developing an application that will be deployed on JBoss mostly, but other application servers might be used as well (Orion, BEA, OC4J etc.) We use log4j to handle logging in the application, and the depoyable EAR-file is "setup" with its own log4j configuration. JBoss uses log4j to log system messages and, needless to say, this log4j configuration collides with the one in our application. In other app-servers that does not use log4j internally this is not an issue. We need a standard way to specify the log4j configuration independent of the application server we are deploying to. It makes total sense to separate the appserver logging from the application's logging. How are folks handling this situation? //Anders -- |===================================================| | Anders Engstr�m | | [EMAIL PROTECTED] | | http://www.gnejs.net | | PGP-Key: http://dmzc.gnejs.net/public_key.asc | |===================================================| | Your mind is like an umbrella. | | It doesn't work unless you open it. | | /Frank Zappa | |===================================================|
msg25949/pgp00000.pgp
Description: PGP signature
