[
https://issues.jboss.org/browse/WFCORE-482?page=com.atlassian.jira.plugin...
]
Nick . edited comment on WFCORE-482 at 4/12/17 11:30 PM:
---------------------------------------------------------
[~jamezp] Its way too old issue now, to answer your question what usually a EAP user
required, a log4j2 module and a log4j2 supportive logging-subsystem. No developers bother
to create an old style log4j.xml if logging-subsystem is configurable wrt log4j2.
So according to me there is no need to support user specific log4j2 configuration via
their xml or properties file, but give enough flexibility in the log4j2 logging
subsystem.
was (Author: nick.sree):
[~jamezp] Its way too old issue now, to answer your question what usually a EAP user
required, a log4j2 module and a log4j2 supportive logging-subsystem. No developers bother
to create an old style log4j.xml if logging-subsystem is configurable wrt log4j2.
Add log4j2 support for WildFly
------------------------------
Key: WFCORE-482
URL:
https://issues.jboss.org/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: Optional
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.2.3#72005)