Ortwin,
We are running jdk 1.4 on both machines. Yes, I will try your System
properties method and see the results. Thanks.
Paul
Ortwin Glück wrote:
paul wrote:
Michael,
Both classpaths are the same and both don't have log4j. The jars
are commons-httpclient-2.0.jar & commons-logging
paul wrote:
Michael,
Both classpaths are the same and both don't have log4j. The jars are
commons-httpclient-2.0.jar & commons-logging.jar . But when compiling,
it have log4j before commons-logging.jar, does it matter?
Paul
Are you running the same JDK version on both machines? Commons-loggi
Michael,
Both classpaths are the same and both don't have log4j. The jars are
commons-httpclient-2.0.jar & commons-logging.jar . But when compiling,
it have log4j before commons-logging.jar, does it matter?
Paul
Michael Becke wrote:
Hi Paul,
Most likely this other machine has log4j on the
Hi Paul,
Most likely this other machine has log4j on the classpath. If present
it will be used. In this case you will have to enable the
httpclient.wire log with log4j.
Mike
On Apr 6, 2004, at 9:58 PM, paul wrote:
Dear all,
I am encountering some peculiar behaviour with printing out th
Dear all,
I am encountering some peculiar behaviour with printing out the wire
logs. Here's what I did in my application :
=
System.setProperty("org.apache.commons.logging.Log",
"org.apache.commons.logging.impl.SimpleLog");
System.setProperty("org.apache.commons.l
