Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Received-SPF: pass (nike.apache.org: domain of ralph.goers@dslextreme.com
 designates 74.125.83.175 as permitted sender)
From: Ralph Goers <ralph.goers@dslextreme.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-8--393320856
Subject: Re: log4j-2.0 questions
Date: Mon, 20 Jun 2011 20:19:20 -0700
In-Reply-To: <04664077-BDF4-4F97-95CE-34E75E55BBA3@seagullsoftware.com>
To: "Log4J Developers List" <log4j-dev@logging.apache.org>
References: 
 <603108.40543.qm@web27801.mail.ukl.yahoo.com>,<BANLkTimtvPeUO5tH4VWvfX+D7DjNqqCm0g@mail.gmail.com>
 <04664077-BDF4-4F97-95CE-34E75E55BBA3@seagullsoftware.com>
Message-Id: <F3635EB3-EAB7-4FC7-92DD-BD2FCEC8C2DA@dslextreme.com>

--Apple-Mail-8--393320856
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jun 20, 2011, at 5:04 PM, Gary Gregory wrote:

>=20
>=20
> On Jun 20, 2011, at 17:33, "ralph.goers @dslextreme.com" =
<ralph.goers@dslextreme.com<mailto:ralph.goers@dslextreme.com>> wrote:
>=20
>=20
> 2.) is there an optional support for ThreadContextClassLoader =
scenarios?
> This is often a problem for logging in libraries which are on a shared =
classpath. Imagine 2 webapps, both using OpenWebBeans as CDI container. =
One webapp sets the org.apache.webbeans loglevel to debug, the other =
wone to WARN ...
>=20
> As it currently stands, no, but I have always intended to introduce =
something to support that.
>=20
> When I wrote the Log4j 2 API it took a stab at creating an abstraction =
to bind the API to an implementation. It was only when I built the core =
that I added the plugin support. Looking at how it is done it now occurs =
to me that the plugin support really should move to the API and be used =
to bind to the implementation. This would provide the flexibility needed =
to accomplish this.
>=20
> How much work us that?


This shouldn't be much work at all. I'll probably do it in the next few =
days.  The only trick is the context selection criteria and making sure =
the LoggerContext and configuration are properly freed when the webapp =
shuts down. Logback uses JNDI lookups (see =
http://logback.qos.ch/manual/loggingSeparation.html#ContextJNDISelector) =
as well as a Servlet Context Listener. I'll probably do somethnig =
similar, although I'd prefer to do it with annotations.

Ralph


--Apple-Mail-8--393320856
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jun 20, 2011, at 5:04 PM, Gary Gregory =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div><br><br>On Jun 20, 2011, at 17:33, "ralph.goers =
@dslextreme.com" &lt;ralph.goers@dslextreme.com&lt;<a =
href=3D"mailto:ralph.goers@dslextreme.com">mailto:ralph.goers@dslextreme.c=
om</a>&gt;&gt; wrote:<br><br><br>2.) is there an optional support for =
ThreadContextClassLoader scenarios?<br> This is often a problem for =
logging in libraries which are on a shared classpath. Imagine 2 webapps, =
both using OpenWebBeans as CDI container. One webapp sets the =
org.apache.webbeans loglevel to debug, the other wone to WARN =
...<br><br>As it currently stands, no, but I have always intended to =
introduce something to support that.<br><br>When I wrote the Log4j 2 API =
it took a stab at creating an abstraction to bind the API to an =
implementation. It was only when I built the core that I added the =
plugin support. Looking at how it is done it now occurs to me that the =
plugin support really should move to the API and be used to bind to the =
implementation. This would provide the flexibility needed to accomplish =
this.<br><br>How much work us =
that?<br></div></blockquote></div><div><br></div><div><br></div><div>This =
shouldn't be much work at all. I'll probably do it in the next few days. =
&nbsp;The only trick is the context selection criteria and making sure =
the LoggerContext and configuration are properly freed when the webapp =
shuts down. Logback uses JNDI lookups (see&nbsp;<a =
href=3D"http://logback.qos.ch/manual/loggingSeparation.html#ContextJNDISel=
ector">http://logback.qos.ch/manual/loggingSeparation.html#ContextJNDISele=
ctor</a>) as well as a Servlet Context Listener. I'll probably do =
somethnig similar, although I'd prefer to do it with =
annotations.</div><div><br></div><div>Ralph</div><br></body></html>=

--Apple-Mail-8--393320856--