Anders Engstr�m <[EMAIL PROTECTED]> writes: >> Remeber that the conf directory is jsut a part of the class path and the >> log4j config file in there is a standard log4j xml config file. I >> usually add my logging information to it.
> Maybe I wasn't clear enough - but this is exactly the scenario we want > to avoid. The deployed application should have a self-contained logging > configuration. There should be no need to modify _server_configuration_ > files to enable/modify logging for a deployed application. I must respectfully disagree. The app server is precisely where you want logging configuration. IMHO, it is very poor form for deployable units to define their own logging parameters. It's akin to packaging their own JDBC drivers in WEB-INF/lib -- ugh!! Something like logging requires centralized control -- it's one of the compelling reasons for using an app server in the first place! What's stopping a poorly-configured app from filling up the disk with log output? The person responsible for disk usage is the sysadmin. He won't be happy having to hunt through his deployed web apps looking for a bad log4j config file. Just my $.02 -- Jim Crossley http://crossleys.org/~jim 404.409.9085 ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
