Author: buildbot
Date: Mon Mar 27 18:47:49 2017
New Revision: 1009168
Log:
Production update by buildbot for cxf
Modified:
websites/production/cxf/content/cache/docs.pageCache
websites/production/cxf/content/docs/debugging-and-logging.html
Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/cxf/content/docs/debugging-and-logging.html
==============================================================================
--- websites/production/cxf/content/docs/debugging-and-logging.html (original)
+++ websites/production/cxf/content/docs/debugging-and-logging.html Mon Mar 27
18:47:49 2017
@@ -116,7 +116,7 @@ Apache CXF -- Debugging and Logging
<td height="100%">
<!-- Content -->
<div class="wiki-content">
-<div id="ConfluenceContent"><ul class="childpages-macro"><li><a shape="rect"
href="general-cxf-logging.html">General CXF Logging</a></li><li><a shape="rect"
href="message-logging.html">Message Logging</a></li><li><a shape="rect"
href="old-message-logging.html">Old Message Logging</a></li><li><a shape="rect"
href="atom-logging.html">ATOM Logging</a></li></ul><h1
id="DebuggingandLogging-DebuggingTools">Debugging Tools</h1><h2
id="DebuggingandLogging-EclipseIDE">Eclipse IDE</h2><p>See this <a shape="rect"
class="external-link"
href="https://web-gmazza.rhcloud.com/blog/entry/eclipse-debug-web-services";
rel="nofollow">blog entry</a> for information on debugging web services using
Eclipse. Note this is primarily for tracing/debugging source code; you will
probably still want to use one of the tools below to capture network traffic,
view SOAP requests and responses, etc.</p><h2
id="DebuggingandLogging-NetBeansIDE">NetBeans IDE</h2><p>NetBeans include a <a
shape="rect" class="external-link"
href="http://www.netbeans.org/features/java/debugger.html";
rel="nofollow">debugger</a>, <a shape="rect" class="external-link"
href="http://www.netbeans.org/features/java/profiler.html";
rel="nofollow">profiler</a> and an HTTP monitor that can assist in
troubleshooting SOA applications.</p><h2
id="DebuggingandLogging-tcpmonandtcptrace">tcpmon and tcptrace</h2><p><a
shape="rect" class="external-link" href="http://tcpmon.dev.java.net";
rel="nofollow">tcpmon</a> allows you to easily view messages as they go back
and forth on the wire. The companion utility <a shape="rect"
class="external-link" href="http://www.tcptrace.org";
rel="nofollow">tcptrace</a> can be used for analysis of the dump.</p><h2
id="DebuggingandLogging-WSMonitor">WSMonitor</h2><p><a shape="rect"
class="external-link" href="https://wsmonitor.dev.java.net/";
rel="nofollow">WSMonitor</a> in another option to Tcpmon with slightly more
functionality.</p><h2 id="DebuggingandLogging-NetSniffer">NetSniffer</h2><p><a
shape="rect"
class="external-link" href="http://www.miray.de/products/sat.netsniffer.html";
rel="nofollow">NetSniffer</a> makes it possible to track the network traffic
between arbitrary devices within a LAN segment.</p><h2
id="DebuggingandLogging-Wireshark">Wireshark</h2><p><a shape="rect"
class="external-link" href="http://www.wireshark.org/";
rel="nofollow">Wireshark</a>, a network packet analyzer, is useful for
following the routing of SOAP messages. It can also help when you are getting
an HTML error message from the server that your CXF client cannot normally
process, by allowing you to see the non-SOAP error message. See this <a
shape="rect" class="external-link"
href="http://www.jroller.com/gmazza/entry/soap_calls_over_wireshark";
rel="nofollow">blog entry</a> for more information.</p><h2
id="DebuggingandLogging-SOAPUI">SOAP UI</h2><p><a shape="rect"
class="external-link" href="http://soapui.org"; rel="nofollow">SOAP UI</a> can
also be used for debugging. In addition to viewing messages, it
allows you send messages and load test your services. It also has plugins for
the <a shape="rect" class="external-link"
href="http://soapui.org/IDE-Plugins/eclipse-plugin.html"; rel="nofollow">Eclipse
IDE</a>, <a shape="rect" class="external-link"
href="http://www.soapui.org/IDE-Plugins/netbean.html"; rel="nofollow">NetBeans
IDE</a> and <a shape="rect" class="external-link"
href="http://www.soapui.org/IDE-Plugins/intellij.html"; rel="nofollow">IntelliJ
IDEA</a>.</p><h1 id="DebuggingandLogging-OtherHelpfulTools">Other Helpful
Tools</h1><h2 id="DebuggingandLogging-WSDLViewer">WSDL Viewer</h2><p><a
shape="rect" class="external-link"
href="http://tomi.vanek.sk/index.php?page=wsdl-viewer"; rel="nofollow">WSDL
Viewer</a> is a small tool to visualize web-services in a more intuitive
way.</p><h1 id="DebuggingandLogging-SOAPFaultfordebugging">SOAP Fault for
debugging</h1><p><strong>This feature is available since CXF
2.3.4</strong></p><h2 id="DebuggingandLogging-Stacktraceinfaultdetails">Stack t
race in fault details</h2><p>CXF supports the ability to put server stack
trace information into the fault message fault details, if you enable the
option of 'faultStackTraceEnabled'. It is useful for debugging if the soap
fault message is not defined in the WSDL operation.</p><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div id="ConfluenceContent"><ul class="childpages-macro"><li><a shape="rect"
href="general-cxf-logging.html">General CXF Logging</a></li><li><a shape="rect"
href="message-logging.html">Message Logging</a></li><li><a shape="rect"
href="old-message-logging.html">Old Message Logging</a></li><li><a shape="rect"
href="atom-logging.html">ATOM Logging</a></li></ul><h1
id="DebuggingandLogging-DebuggingTools">Debugging Tools</h1><h2
id="DebuggingandLogging-EclipseIDE">Eclipse IDE</h2><p>See this <a shape="rect"
class="external-link"
href="https://web-gmazza.rhcloud.com/blog/entry/eclipse-debug-web-services";
rel="nofollow">blog entry</a> for information on debugging web services using
Eclipse. Note this is primarily for tracing/debugging source code; you will
probably still want to use one of the tools below to capture network traffic,
view SOAP requests and responses, etc.</p><h2
id="DebuggingandLogging-NetBeansIDE">NetBeans IDE</h2><p>NetBeans include a <a
shape="rect" class="external-link"
href="http://www.netbeans.org/features/java/debugger.html";
rel="nofollow">debugger</a>, profiler, and an HTTP monitor that can assist
in troubleshooting SOA applications.</p><h2
id="DebuggingandLogging-tcpmonplus">tcpmonplus</h2><p><a shape="rect"
class="external-link" href="https://sourceforge.net/projects/tcpmonplus/";
rel="nofollow">tcpmonplus</a> allows you to easily view messages as they go
back and forth on the wire.</p><h2
id="DebuggingandLogging-WSMonitor">WSMonitor</h2><p><a shape="rect"
class="external-link"
href="https://java.net/projects/wsmonitor/sources/svn/show/trunk/wsmonitor?rev=97";
rel="nofollow">WSMonitor</a> in another option to Tcpmon with slightly more
functionality.</p><h2 id="DebuggingandLogging-NetSniffer">NetSniffer</h2><p><a
shape="rect" class="external-link"
href="http://www.miray.de/products/sat.netsniffer.html";
rel="nofollow">NetSniffer</a> makes it possible to track the network traffic
between arbitrary devices within a LAN segment.</p><h2 id="Deb
uggingandLogging-Wireshark">Wireshark</h2><p><a shape="rect"
class="external-link" href="http://www.wireshark.org/";
rel="nofollow">Wireshark</a>, a network packet analyzer, is useful for
following the routing of SOAP messages. It can also help when you are getting
an HTML error message from the server that your CXF client cannot normally
process, by allowing you to see the non-SOAP error message.</p><h2
id="DebuggingandLogging-SOAPUI">SOAP UI</h2><p><a shape="rect"
class="external-link" href="http://soapui.org"; rel="nofollow">SOAP UI</a> can
also be used for debugging. In addition to viewing messages, it allows you send
messages and load test your services. It also has plugins for the <a
shape="rect" class="external-link"
href="http://soapui.org/IDE-Plugins/eclipse-plugin.html"; rel="nofollow">Eclipse
IDE</a>, <a shape="rect" class="external-link"
href="http://www.soapui.org/IDE-Plugins/netbean.html"; rel="nofollow">NetBeans
IDE</a> and <a shape="rect" class="external-link" href="http
://www.soapui.org/IDE-Plugins/intellij.html" rel="nofollow">IntelliJ
IDEA</a>.</p><h1 id="DebuggingandLogging-OtherHelpfulTools">Other Helpful
Tools</h1><h2 id="DebuggingandLogging-WSDLViewer">WSDL Viewer</h2><p><a
shape="rect" class="external-link"
href="http://tomi.vanek.sk/index.php?page=wsdl-viewer"; rel="nofollow">WSDL
Viewer</a> is a small tool to visualize web-services in a more intuitive
way.</p><h1 id="DebuggingandLogging-SOAPFaultfordebugging">SOAP Fault for
debugging</h1><h2 id="DebuggingandLogging-Stacktraceinfaultdetails">Stack trace
in fault details</h2><p>CXF supports the ability to put server stack trace
information into the fault message fault details, if you enable the option of
'faultStackTraceEnabled'. It is useful for debugging if the soap fault message
is not defined in the WSDL operation.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="brush: java; gutter: false; theme: Default"
style="font-size:12px;"><jaxws:endpoint id="server"
address="http://localhost:9002/TestMessage";
wsdlURL="ship.wsdl"
endpointName="s:TestSoapEndpoint"
