Logging levels follow a very strict hierarchical scheme
So in one instance you may very well assume you're writing debug statements at a inherited level but are unable to do so as the DEBUG level was disabled upstream
following the example
// get a logger instance named "com.foo"
   Logger  logger = Logger.getLogger("com.foo");

   // Now set its level. Normally you do not need to set the
   // level of a logger programmatically. This is usually done
   // in configuration files.
   logger.setLevel(Level.INFO);

   Logger barlogger = Logger.getLogger("com.foo.Bar");

   // This request is enabled, because WARN >= INFO.
   logger.warn("Low fuel level.");

   // This request is disabled, because DEBUG < INFO.
   logger.debug("Starting search for nearest gas station.");
I found this tutorial helpful (courtesy of Courtesy of Ceki Gulcu)
 
*********************************************************************
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.
 

 
----- Original Message -----
From: xu cai
Sent: Sunday, July 23, 2006 3:20 AM
Subject: Re: [Axis 1.4] how to setup log4j.properties at Axis client side

ok, thanks.
I finally get what I need.
Just put log4j.properties to axis.jar, and change the logging level to "DEBUG".
 
On 7/21/06, Martin Gainty <[EMAIL PROTECTED]> wrote:
In that situation use whatever logging mechanism you set up to capture stdout or stderr stream
GL.
*********************************************************************
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.
 

 
----- Original Message -----
From: xu cai
Sent: Friday, July 21, 2006 3:32 AM
Subject: Re: [Axis 1.4] how to setup log4j.properties at Axis client side

 
sorry, you may not understand me.
 
I want to see the client side log.
 
currently the soap request can't be generated well, I need to know what happens on client side.

 
On 7/21/06, 蘇 軼(CEC) < [EMAIL PROTECTED]> wrote:
hi xucai,

try
1. create log4j.properties:
2. copy to webapps/$your-application/WEB_INF/classes
3. restart Tomcat

maybe it works ...

- sukie

----- Original Message -----
From: xu cai
To: [email protected]
Sent: Friday, July 21, 2006 3:23 PM
Subject: [Axis 1.4] how to setup log4j.properties at Axis client side


Hi All,
     I am testing my web-service using Axis, and how to setup log
enviroment at client side.
where  should I put log4j.properties ? on classpath ? , but I still can't
see any log information or log file generated.


- xucai


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
- xucai



--
- xucai

Reply via email to