You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by di...@apache.org on 2002/08/04 13:53:30 UTC
cvs commit: jakarta-commons/httpclient/xdocs logging.xml
dion 2002/08/04 04:53:30
Modified: httpclient/xdocs logging.xml
Log:
Fix bad xml
Revision Changes Path
1.2 +5 -5 jakarta-commons/httpclient/xdocs/logging.xml
Index: logging.xml
===================================================================
RCS file: /home/cvs/jakarta-commons/httpclient/xdocs/logging.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- logging.xml 2 Aug 2002 19:45:31 -0000 1.1
+++ logging.xml 4 Aug 2002 11:53:30 -0000 1.2
@@ -26,20 +26,20 @@
to write log messages. All the following examples are shown with
SimpleLog to highlight the utility withing <em>HttpClient</em>
</p><p>
- <u>log</u><br>
+ <u>log</u><br />
The logging output can be configured on a class by class basis if
desired. This is accomplished by setting a system property for
each class. For example, if you wanted to see extremely detailed
information on authentication routines, you could turn up the
logging level for the Authenticator by setting the following
- property:<br>
+ property:<br />
org.apache.commons.logging.simplelog.log.org.apache.commons.httpclient.Authenticator=trace
</p><p>
- <u>wireLog</u><br>
+ <u>wireLog</u><br />
There is one log that cuts across several classes that is used for
logging wire messages. <i>Careful when turning this on as
potentially a huge volume of data may be written, some of it in
- binary format.</i><br>
+ binary format.</i><br />
org.apache.commons.logging.simplelog.log.httpclient.wire=debug
</p><p>
TODO: put the logging guidelines here
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>