[
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.
Sort out logging for OSGi deployment
------------------------------------
Key: JBESB-2211
URL:
https://jira.jboss.org/jira/browse/JBESB-2211
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Rosetta
Reporter: Tom Fennelly
Assignee: Daniel Bevenius
Fix For: 5.0 initial development
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.
--
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