From c0d3fbc4f6023e8a014a6d663d936e74cc4a87ab Mon Sep 17 00:00:00 2001
From: Jonathan Robie <jonathan@apache.org>
Date: Mon, 28 Jun 2010 21:48:43 +0000
Subject: Modified the wording for the log4j section.

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@958753 13f79535-47bb-0310-9956-ffa450edef68
---
 qpid/doc/book/src/Programming-In-Apache-Qpid.xml | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

(limited to 'qpid/doc')

diff --git a/qpid/doc/book/src/Programming-In-Apache-Qpid.xml b/qpid/doc/book/src/Programming-In-Apache-Qpid.xml
index f44ef4b178..705ce06c12 100644
--- a/qpid/doc/book/src/Programming-In-Apache-Qpid.xml
+++ b/qpid/doc/book/src/Programming-In-Apache-Qpid.xml
@@ -3045,17 +3045,15 @@ producer.send(m);
     
     <section id="section-JMS-Logging">
       <title>JMS Client Logging</title>
-      <para>The JMS Client logging is handled using <ulink url="http://www.slf4j.org/">SLF4J</ulink>. A user can place a slf4j binding of their choice in the classpath and configure the respective logging mechanism to suit their needs. Ex bindings include log4j, jdk1.4 logging ..etc</para>
+      <para>The JMS Client logging is handled using the Simple Logging Facade for Java (<ulink url="http://www.slf4j.org/">SLF4J</ulink>). As the name implies, slf4j is a facade that delegates to other logging systems like log4j or JDK 1.4 logging. For more information on how to configure log4j for specific logging systems, please consult the log4j documentation.</para>
 
-      <para>Following is an example on how to configure the client logging with the log4j binding.</para>
+      <para>When using the log4j binding, please set the log level for org.apache.qpid explicitly. Otherwise log4j will default to DEBUG which will degrade performance considerably due to excessive logging. The recommended logging level for production is <literal>WARN</literal>.</para>
 
-      <para>For more information on how to configure log4j, please consult the log4j documentation.</para>
-
-      <para>If using the log4j binding please ensure to set the log level for org.apache.qpid explicitly. Otherwise log4j will default to DEBUG which will degrade performance considerably due to excessive logging. Recommended logging level for production is WARN.</para>
+      <para>The following example shows the logging properties used to configure client logging for slf4j using the log4j binding. These properties can be placed in a log4j.properties file and placed in the <varname>CLASSPATH</varname>, or they can be set explicitly using the -Dlog4j.configuration property.</para>
 
       <example>
 	<title>log4j Logging Properties</title>
-	<para>You could place the snippet below in a log4j.properties file and place it in the classpath or explicitly specify it using the -Dlog4j.configuration property. The following configures the qpid client to log at the WARN level</para>
+
 	<programlisting><![CDATA[
 log4j.logger.org.apache.qpid=WARN, console
 log4j.additivity.org.apache.qpid=false
@@ -3066,7 +3064,9 @@ log4j.appender.console.layout=org.apache.log4j.PatternLayout
 log4j.appender.console.layout.ConversionPattern=%t %d %p [%c{4}] %m%n
 ]]></programlisting>
       </example> 
+
     </section>
+
   </chapter>
 
   <chapter id="QpidWCF">
-- 
cgit v1.2.1