[
https://issues.redhat.com/browse/WFCORE-482?page=com.atlassian.jira.plugi...
]
James Perkins commented on WFCORE-482:
--------------------------------------
[~walkerca] I don't think so as the {{Appender}} interface is part of the
{{org.apache.logging.log4j:log4j-core}} project which is a full log manager
implementation. There is no current plan to fork log4j2 which would be required for that
to happen I'd think. It's something that could be researched at some point
though.
For the integration the main idea is that if you just use the {{log4j-api}} then it will
have an implementation that writes to the jboss-logmanager. One idea I would like to
implement and do have it working, but it's a bit clumsy, is if you include
{{log4j-core}} in a deployment that it would take over the log manager duties for the
deployment.
Do you have some expectations on how you'd expect it to work? That's the main
thing that has held up the integration work, besides time :), is I'm not sure what end
users expect.
Add log4j2 support for WildFly
------------------------------
Key: WFCORE-482
URL:
https://issues.redhat.com/browse/WFCORE-482
Project: WildFly Core
Issue Type: Task
Components: Logging
Environment: Spring 3, Hibernate, Wicket, JBoss AS7
Reporter: Amarkanth Ranganamayna
Assignee: James Perkins
Priority: Major
I am trying to use Flume Appender which comes with Log4j2 (log4j 1.x doesn't support
flume appender) (AND) inorder to acheive this, I am looking at how to configure JBoss AS7
to use log4j2.
Looks like Jboss AS7 by default use log4j 1.x
Are you guys already working on using log4j2 ?
If NOT, can you please suggest how to configure Jboss AS7 such that it picks up
"log4j2.xml" file and doesn't use its own logging.
Thanks,
Amar
--
This message was sent by Atlassian Jira
(v7.13.8#713008)