Brent,
I am using log4j.properties instead of log4j.xml.
Will RepositorySelector concept still work? What changes I should make
into this method?
private static void loadLog4JConfig(ServletConfig config,
Hierarchy hierarchy)
throws ServletException {
try {
String log4jFile = "/WEB-INF/log4j.xml";
InputStream log4JConfig =
config.getServletContext().getResourceAsStream(log4jFile);
Document doc = DocumentBuilderFactory.newInstance()
.newDocumentBuilder()
.parse(log4JConfig);
DOMConfigurator conf = new DOMConfigurator();
conf.doConfigure(doc.getDocumentElement(), hierarchy);
} catch (Exception e) {
throw new ServletException(e);
}
}
From: Brent Worden <[email protected]>
To: [email protected]
Date: 08/09/2010 09:56 AM
Subject: Re: [Logging] : Can commons.logging be used without log4j
On 8/9/2010 7:53 AM, Jasmin Mehta wrote:
> The log4j has limitation that if its used as a shared library then it
can
> initiate only one configuration. So my all we applications which shares
> the same instance are populating the logs into only one log file (the
web
> app which deployed first in order), rather than individual / separate
log
> files configured in the path of each of the application's
> log4j.properties.
>
>
This isn't true. Log4j allows for defining and using multiple log
configurations in a single JVM. This is accomplished by using a
RepositorySelector to manage the multiple log hierarchies. See
http://community.jboss.org/wiki/Log4jrepositoryselector for a web
container example.
Thanks,
Brent Worden
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
******************************************************************************
This email and any files transmitted with it are intended solely for
the use of the individual or agency to whom they are addressed.
If you have received this email in error please notify the Navy
Exchange Service Command e-mail administrator. This footnote
also confirms that this email message has been scanned for the
presence of computer viruses.
Thank You!
******************************************************************************
