I think I was somehow wrong. Sorry. So far I have configured log4j in log4j.properties for the tomcat environment by placing log4j.properties at Tomcat and Axis2 classpath. So log4j works properly.
But NOW I am at client side, any maybe someone can tell me how to make, that I can use, log4j loggers at client side when I start the jaxws-samples/SampleClient in debug mode? Josef Von: Stadelmann Josef [mailto:josef.stadelm...@axa-winterthur.ch] Gesendet: Dienstag, 3. April 2012 11:40 An: java-user@axis.apache.org Betreff: [axis2-1.6.1] why log4j and Jdk14 loggers in the same system? Why does public class org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler extends BindingProvider implements InvocationHandler { private static Log log = LogFactory.getLog(JAXWSProxyHandler.class); engage a Jdk14Logger and break all my log4j setups? I went deep on debugging and turning on log4j loggers as I need em. They all work. Today I encountered during debugging the statement above and went to add a log4j logger. However no output ws generated because debug is always false. Then I detected that I was wrong and the logger above is in fact a Jdk14 logger. Is there a known way to configure for booth type of loggers? Please help or correct this with a future version, I can not see any good to have two different logger systems engaged in a single already complex system. Josef
