> I couldn’t find anything explaining this, so I thought I’d share it.
This likely should go on the Wiki. Most of the important points of your configuration below are mentioned in the files that ship with CAS, but I admit it would be nice to have some step-by-step instructions to accompany the comments in the files. > a) Remove or rename CAS’ WEB-INF/classes/log4j.properties to something > that won’t be read. We should explain how to do with with the Maven War overlay process. log4j.properties has this comment at the top: # For JBoss: Avoid to setup Log4J outside $JBOSS_HOME/server/default/deploy/log4j.xml! It would be helpful to demonstrate how to do that via Maven War overlay. > b) In web.xml comment out Log4jConfigListener. I believe that is pretty well documented in the web.xml file that ships with CAS, but again, stepwise instructions are good. > c) In web.xml comment out log4jConfigLocation and > log4jExposeWebAppRoot. This isn't strictly necessary since these context params are unused if Log4jConfigListener is not active. It's probably a good idea to remove them altogether, though, on JBoss. > d) Remove or rename WEB-INF/lib/log4j*.jar to a non-jar extension so > that jBoss’ customized log4j can take over. I recall that this is required from when we deployed on JBoss. http://docs.jboss.org/process-guide/en/html/logging.html doesn't explicitly say to exclude log4j.jar from deployables, but it does say that you MUST include log4j.jar and do classloader magic to do per-app logging. I think it's reasonable to require the exclusion of log4j.jar when deploying on JBoss to enable the standard container-managed logging via jboss-log4j.xml. Again, the recommended way to exclude a jar is via Maven War overlay. I hope you'll consider posting stepwise instructions to the CASUM Wiki. 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
