[ https://jira.jboss.org/jira/browse/JBESB-2211?page=com.atlassian.jira.plu... ] Tom Fennelly updated JBESB-2211: -------------------------------- Description: We currently have log4j configs in places where they shouldn't be. There's an OSGi LogService. Not sure how we can hook in log4j without polluting code with OSGi LogService code. There should be a way. Maybe there's an OSGi LogService log4j appender , or something like that. was: We currently have log4j configs in places where they shouldn't be. There's an OSGi LogService. Not sure how we can log4j into this without polluting code with OSGi code. There should be a way. Maybe there's an OSGi LogService log4j appender , or something like that. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-2211?page=com.atlassian.jira.plu... ] Work on JBESB-2211 started by Daniel Bevenius. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-2211?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-2211: ------------------------------------- Look at the pax logging code from ops4j as it has delegates for some of the other frameworks, including log4j. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira