On 19 Nov 2003, at 18:25, Richard Sitze wrote:
Regarding a "pluggable" LogFactory. It's already there.
Unfortunately,
it's behaviour isn't ideal... Log4J seems to have taken a pre-emenant
place in the scheme of things. [That's been discussed before, forgive
me
for not digging up the details
hi richard
On 18 Nov 2003, at 19:51, Richard Sitze wrote:
So, I'm coming into this a bit late and all, and I know a few others
have
been looking at this over the past few weeks... hope this does more
than
just add fuel to the fire.
commons-discovery was created to address the classloader usag
inal Message -
From: "Richard Sitze" <[EMAIL PROTECTED]>
To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, November 18, 2003 12:51 PM
Subject: RE: commons-logging & classloading (continued)
> So, I'm coming into this a bit late
wrote:
> Well put Norbert.
> I think that since classloading and threads are such complex
> issues there should be a way to not use the pattern
> of loading the implementation from thread's context classloader.
> (Hint to Craig :)
>
> - rami
>
> >-Original Message-
Will Jaynes wrote:
Well, I submitted this as a bug and included a patch. But Remy
immediately marked it as RESOLVED/WONTFIX. He doesn't really address my
suggestion other than to say that c-l "if used properly ... is well
thought out, and works perfectly well" I would never suggest that c-l is
Will Jaynes wrote:
robert burrell donkin wrote:
...
2, a more sophisticated implementation for the loading of the
LogFactory implementation that would try to load the class from the
LogFactory class classloader if the assignment fails. since (at the
moment) we throw an exception in this circu
n from thread's context classloader.
> (Hint to Craig :)
>
> - rami
>
> >-Original Message-
> >From: Norbert Klose [mailto:[EMAIL PROTECTED]
> >Sent: Thursday, October 30, 2003 12:21 PM
> >To: [EMAIL PROTECTED]
> >Subject: commons-loggi
L PROTECTED]
>Sent: Thursday, October 30, 2003 12:21 PM
>To: [EMAIL PROTECTED]
>Subject: commons-logging & classloading (continued)
>
>
>Hello,
>
>i currently use Tomcat 4.1.27 bundled with commons-logging
>1.0.3. My own webapp i'm working on also uses commons
Hello,
i currently use Tomcat 4.1.27 bundled with commons-logging 1.0.3. My own webapp i'm
working on also uses commons-logging, so i include a copy of the jar file into the
WEB-INF/lib directory to be protable to other servlet containers that does not include
the commons-logging package. I fou
