[
https://jira.jboss.org/jira/browse/JBCOMMON-63?page=com.atlassian.jira.pl...
]
Dimitris Andreadis closed JBCOMMON-63.
--------------------------------------
Resolution: Won't Fix
Galder, with the latest changes in 5.1 we have a jdk logging bridge that allows
java.util.logging.Logger to output to the jboss log, plus allow the setting of
j.u.l.Logger levels in the jboss-log4j.xml.
JDK to Log4j/JBoss logging handler
----------------------------------
Key: JBCOMMON-63
URL:
https://jira.jboss.org/jira/browse/JBCOMMON-63
Project: JBoss Common
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: common-logging-jdk, common-logging-log4j
Reporter: Galder ZamarreƱo
Assignee: Galder ZamarreƱo
Attachments: logging-jbcommon.zip
Certain 3rd party libraries log using JDK logging and customers want to
see these applications logging to where JBoss logs. We should provide
a JDK logging handler than logs using log4j or JBoss logging API. Please
find attached a handler I created to log to log4j. Creating a handler for log4j
was easier than creating one for JBoss logging because of the presence
of Logger.log(Level, String...) API in 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