Yup - found it / fixed it. I had transcribed log4j.category to
log4j.logger.
That was it. Thanks much.
Cheers,
David
From: "David Brady" <[EMAIL PROTECTED]>
Reply-To: "Commons HttpClient Project"
<[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: W
David,
You might try setting the logging level for the "Logger" called
"httpclient.wire".
In other words, add this:
log4j.category.httpclient.wire=
Alas, I already had it in my log4j.properties file from my experiments over
the weekend. Didn't impact wire logging levels at all:
log4j.
David,
You might try setting the logging level for the "Logger" called
"httpclient.wire".
In other words, add this:
log4j.category.httpclient.wire=
with the debug level of your choice. If you look carefully at the
logging.html page, you can dig this tidbit out from this line:
"System.set
I use Log4j for our current project - no problems with it.
I've added to our log4j.properties file:
log4j.category.org.apache=INFO
This represses all of the httpclient debug messages (great!), but it doesn't
impact the "wire" debug messages.
Am I missing something?
I've checked the logging do
