[jboss-dev] 2nd console appender
I don't see any justification of having by default 2 active ConsoleAppenders at
different
levels (INFO and TRACE), just so the following can be easily enabled.
<!-- Enable JBossWS message tracing
<category name="jbossws.SOAPMessage">
<appender-ref ref="SOAPMessageAppender"/>
<priority value="TRACE" class="org.jboss.logging.XLevel"/>
</category>
-->
jboss-cvs-commits(a)lists.jboss.org wrote:
Author: thomas.diesler(a)jboss.com
Date: 2007-03-23 12:18:02 -0400 (Fri, 23 Mar 2007)
New Revision: 61642
Modified:
branches/Branch_4_2/server/src/etc/conf/default/jboss-log4j.xml
Log:
Add SOAPMessageAppender
Modified: branches/Branch_4_2/server/src/etc/conf/default/jboss-log4j.xml
===================================================================
--- branches/Branch_4_2/server/src/etc/conf/default/jboss-log4j.xml 2007-03-23 16:17:39
UTC (rev 61641)
+++ branches/Branch_4_2/server/src/etc/conf/default/jboss-log4j.xml 2007-03-23 16:18:02
UTC (rev 61642)
@@ -72,6 +72,17 @@
</layout>
</appender>
+ <appender name="SOAPMessageAppender"
class="org.apache.log4j.ConsoleAppender">
+ <errorHandler
class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
+ <param name="Target" value="System.out"/>
+ <param name="Threshold" value="TRACE"/>
+
+ <layout class="org.apache.log4j.PatternLayout">
+ <!-- The default pattern: Date Priority [Category] Message\n -->
+ <param name="ConversionPattern" value="%d{ABSOLUTE} %-5p
[%c{1}] %m%n"/>
+ </layout>
+ </appender>
+
<!-- ====================== -->
<!-- More Appender examples -->
<!-- ====================== -->
@@ -192,6 +203,7 @@
<!-- Enable JBossWS message tracing
<category name="jbossws.SOAPMessage">
+ <appender-ref ref="SOAPMessageAppender"/>
<priority value="TRACE"
class="org.jboss.logging.XLevel"/>
</category>
-->
_______________________________________________
jboss-cvs-commits mailing list
jboss-cvs-commits(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-cvs-commits