[ https://issues.jboss.org/browse/JBRULES-3572?page=com.atlassian.jira.plug... ] Cristiano Nicolai commented on JBRULES-3572: -------------------------------------------- I think I got it figured out, from Jboss 7.1.2 a per-deployment logging configuration has been introduced. Jboss detects if there is any logging config file in the classpath, if so, it creates a separated log context. As explained on this thread: https://community.jboss.org/thread/199923 In order to make Guvnor use the main Jboss logging subsystem I had to do the following steps: 1- Remove all logging jars from WEB-INF\lib. (slf4j*, log4j-1.2.12.jar and commons-logging-1.0.4.jar) 2- Remove log4j.xml from WEB-INF\classes 3- Upgrade webdav-servlet dependency from 2.0 to 2.0.1 because the current version includes a log4j.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBRULES-3572?page=com.atlassian.jira.plug... ] Geoffrey De Smet commented on JBRULES-3572: ------------------------------------------- 1 and 2 could be done in the jboss AS specific assembly: https://github.com/droolsjbpm/guvnor/blob/master/guvnor-distribution-wars... But, personally, I don't know if I like "2- Remove log4j.xml from WEB-INF\classes" Why? Because the guvnor war is an end-user application (unlike drools-core, drools-planner or jbpm-flow which are not end-user apps and should therefor have no logging configuration in them). So, as an end-user, you expect the logging of guvnor to be sensible defaulted and happening. This means A) it goes to a file (not /dev/null) and B) it's probably filtered by default on level WARN or maybe INFO (but not DEBUG or TRACE). So C) it guarantees that a guvnor warn message shows up in a file somewhere, even if the user is using it out-of-the-box. If jboss logging does A), B) and C) automatically if we fulfill 1) and 2) in the AS specific assembly, then I am +1 for such changes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBRULES-3572?page=com.atlassian.jira.plug... ] Geoffrey De Smet edited comment on JBRULES-3572 at 7/19/12 11:05 AM: --------------------------------------------------------------------- 1 and 2 could be done in the jboss AS specific assembly: https://github.com/droolsjbpm/guvnor/blob/master/guvnor-distribution-wars... But, personally, I don't know if I like "2- Remove log4j.xml from WEB-INF\classes" Why? Because the guvnor war is an end-user application (unlike drools-core, drools-planner or jbpm-flow which are not end-user apps and should therefor have no logging configuration in them). So, as an end-user, you expect the logging of guvnor to be sensible defaulted and happening. This means A) it goes to a file (not /dev/null) and B) it's probably filtered by default on level WARN or maybe INFO (but not DEBUG or TRACE). So C) it guarantees that a guvnor warn message shows up in a file somewhere, even if the user is using it out-of-the-box. If jboss AS 7 logging does A), B) and C) automatically if we fulfill 1) and 2) in the AS specific assembly, then I am +1 for such changes (and I 'll merge a good pull request with such changes). was (Author: ge0ffrey): 1 and 2 could be done in the jboss AS specific assembly: https://github.com/droolsjbpm/guvnor/blob/master/guvnor-distribution-wars... But, personally, I don't know if I like "2- Remove log4j.xml from WEB-INF\classes" Why? Because the guvnor war is an end-user application (unlike drools-core, drools-planner or jbpm-flow which are not end-user apps and should therefor have no logging configuration in them). So, as an end-user, you expect the logging of guvnor to be sensible defaulted and happening. This means A) it goes to a file (not /dev/null) and B) it's probably filtered by default on level WARN or maybe INFO (but not DEBUG or TRACE). So C) it guarantees that a guvnor warn message shows up in a file somewhere, even if the user is using it out-of-the-box. If jboss AS 7 logging does A), B) and C) automatically if we fulfill 1) and 2) in the AS specific assembly, then I am +1 for such changes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira