[
https://issues.jboss.org/browse/AS7-4925?page=com.atlassian.jira.plugin.s...
]
Ravi Luthra edited comment on AS7-4925 at 7/10/12 6:02 PM:
-----------------------------------------------------------
One curiosity of mine is translation -
If an application logs with Log4J, is there any translation between that log event and the
log4j appender in JBoss (as managed by the log manager after this bug is fixed)?
I can understand a translation occurring if the log event comes from JUL, Commons, or SLF
- but if Log4J is the logging API and the Handling API - I'm hoping we can get the
original event object.
Reason I ask is we have a couple of APIs that would like to use Log4J's Object
parameter to pump in special objects - and Log4J retains these objects in the LoggingEvent
that gets sent to the Appender. However if this is not possible and the message gets
converted to a String - we'll understand this as one of the unfortunate side effects
of the logmanager subsystem. Our work-around would be to include a special appender in
log4J's root logger that would hopefully not get closed or otherwise managed by JBoss
- and from that appender we can perform our special logging.
Overall this is probably the only EAP 5 to 6 transitional item we had a gap on.
was (Author: homer400):
One curiosity of mine is translation -
If an application logs with Log4J, is there any translation between that log event and the
log4j appender in JBoss (as managed by the log manager after this bug is fixed)?
I can understand a translation occurring if the log even comes from JUL, Commons, or SLF -
but if Log4J is the logging API and the Handling API - I'm hoping we can get the
original event object.
Reason I ask is we have a couple of APIs that would like to use Log4J's Object
parameter to pump in special objects - and Log4J retains these objects in the LoggingEvent
that gets sent to the Appender. However if this is not possible and the message gets
converted to a String - we'll understand this as one of the unfortunate side effects
of the logmanager subsystem. Our work-around would be to include a special appender in
log4J's root logger that would hopefully not get closed or otherwise managed by JBoss
- and from that appender we can perform our special logging.
Overall this is probably the only EAP 5 to 6 transitional item we had a gap on.
Log4j appenders should also be allowed for custom handlers
----------------------------------------------------------
Key: AS7-4925
URL:
https://issues.jboss.org/browse/AS7-4925
Project: Application Server 7
Issue Type: Bug
Components: Logging
Reporter: James Perkins
Assignee: James Perkins
Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
Currently custom handlers only allows for a {{java.util.logging.Handler}}. log4j
appenders also need to be allowed and configured.
--
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