> BTW, for those using Tomcat, if you have the log4j JAR and dependencies plus > a log4j.xml in the Tomcat lib folder... you get the same centralized log4j > behavior as you do in jBoss. It sure beats having to configure log4j for > each app!
Having worked with deployments on both JBoss and Tomcat, I think it's a philosophical difference between platforms regarding log configuration management. It's definitely "The JBoss Way" to do centralized logging with one file controlling the appenders and categories for all applications in the container. In Tomcat, the model is "to each application its own." My personal preference is for the latter, but I would think sticking to the conventions of the platform is best. In fact you can really screw up logging in JBoss by trying to configure application-specific logging. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
