robert burrell donkin [EMAIL PROTECTED] wrote on 01/30/2005 04:09:54
PM:
On 28 Jan 2005, at 20:15, Richard Sitze wrote:
[re-send.. I don't see this picked up... hmmm]
Once, a long long time ago... someone wrote:
The problem: it won't work if commons-logging.jar is installed in
On Tue, 2005-02-01 at 20:27, Richard Sitze wrote:
robert burrell donkin [EMAIL PROTECTED] wrote on 01/30/2005 04:09:54
PM:
On 28 Jan 2005, at 20:15, Richard Sitze wrote:
[re-send.. I don't see this picked up... hmmm]
Once, a long long time ago... someone wrote:
The
On 2005-01-28 20:15:13, Richard Sitze wrote:
[re-send.. I don't see this picked up... hmmm]
I intend to respond to your message in detail as soon as I get a chance.
It's at the top of my to do list.
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
On 28 Jan 2005, at 20:15, Richard Sitze wrote:
[re-send.. I don't see this picked up... hmmm]
Once, a long long time ago... someone wrote:
The problem: it won't work if commons-logging.jar is installed in the
parent class loader, and log4j.jar ( or another logger ) is installed
in a child loader (
Once, a long long time ago... someone wrote:
The problem: it won't work if commons-logging.jar is installed in the
parent class loader, and log4j.jar ( or another logger ) is installed
in a child loader ( like WEB-INF/lib ).
What happens:
- the factory uses the thread class loader to check
