[weld-commits] Weld SVN: r5093 - doc/trunk/reference/en-US.

[weld-commits at lists.jboss.org]

Author: gavin.king at jboss.com
Date: 2009-11-17 22:47:29 -0500 (Tue, 17 Nov 2009)
New Revision: 5093

Modified:
   doc/trunk/reference/en-US/extensions.xml
Log:
waffle

Modified: doc/trunk/reference/en-US/extensions.xml
===================================================================
--- doc/trunk/reference/en-US/extensions.xml	2009-11-18 03:37:04 UTC (rev 5092)
+++ doc/trunk/reference/en-US/extensions.xml	2009-11-18 03:47:29 UTC (rev 5093)
@@ -35,15 +35,9 @@
 }]]></programlisting>
 
       <para>
-         The example shows how objects can be interpolated into a message. This interpolation is done using
-         <emphasis>java.text.MessageFormat</emphasis>, so see the JavaDoc for that class for more details. In this case,
-         the <literal>ShoppingCart</literal> should have implemented the <emphasis>toString()</emphasis> method to
-         produce a human readable value that is meaningful in messages. Normally, this call would have involved
-         evaluating cart.toString() with String concatenation to produce a single String argument. Thus it was necessary
-         to surround the call with an if-statement using the condition <emphasis>log.isDebugEnabled()</emphasis> to
-         avoid the expensive String concatenation if the message was not actually going to be used. However, when using
-         <literal>@Logger</literal>-injected logging, the conditional test can be left out since the object arguments
-         are not evaluated unless the message is going to be logged.
+         The example shows how objects can be interpolated into a message. If you use this approach, you do not need to 
+         surround a call to the logger with a condition like <emphasis>if ( log.isDebugEnabled() )</emphasis> to
+         avoid string concatenation.
       </para>
       
       <note>