THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Code Block | ||||
---|---|---|---|---|
| ||||
<target name="runClient"> <java classname="client.WSClient" fork="true"> <classpath> <pathelement location="${build.classes.dir}"/> <fileset dir="${env.CXF_HOME}/lib"> <include name="*.jar"/> </fileset> </classpath> <jvmarg value="-Djava.util.logging.config.file=/usr/myclientapp/logging.properties"/> </java> </target> |
Using Log4j Instead of java.util.logging
As noted above, CXF uses the java.util.logging
package by default. But it is possible to switch CXF to instead use Log4J. This is achieved through the use of configuration files. There are two options to bootstrapping CXF logging and each is listed below:
- Add the following system property to the classpath from which CXF is initialized:
Code Block |
---|
-Dorg.apache.cxf.Logger=org.apache.cxf.common.logging.Log4jLogger
|
- Add the file
META-INF/cxf/org.apache.cxf.Logger
to the classpath and make sure it contains the following content:
Code Block |
---|
org.apache.cxf.common.logging.Log4jLogger
|
Debugging Tools
Eclipse IDE
...