This content has been marked as final.
Show 2 replies
-
1. Re: wstools and Log4J
sam.griffith Dec 10, 2006 5:41 AM (in response to martinconnolly)Martin,
I'm not sure about the C# calls failure, but as far as the log appender, you can put the following log4j code in a log4j.xml file in your WS build dir so it gets packaged up with your WS when deployed and it'll be used as the appender. You don't have an appender defined for the WSTools so this one will serve as a default. I'll try and look into a more correct way to define the logger for WSTools when it's being invoked but in the mean time this should help get rid of that message.<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd"> <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/" debug="false"> <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender"> <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/> <param name="Target" value="System.out"/> <param name="Threshold" value="INFO"/> <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> <root> <appender-ref ref="CONSOLE"/> </root> </log4j:configuration>
-
2. Re: wstools and Log4J
martinconnolly Dec 11, 2006 5:35 AM (in response to martinconnolly)thanks Sam. Will try this out.
MC