|
|
|
@ -16,8 +16,8 @@ Debugging with Smack
|
|
|
|
|
|
|
|
|
|
<p>
|
|
|
|
|
Smack includes two built-in debugging consoles that will let you track all XML traffic between
|
|
|
|
|
the client and server. A <a href="#lite">lite debugger</a> which is part of the <tt>smack.jar</tt>
|
|
|
|
|
and an <a href="#enhanced">enhanced debugger</a> contained in <tt>smackx-debug.jar</tt>.
|
|
|
|
|
the client and server. A <a href="#lite">lite debugger</a> which is part of the <tt>smack-core.jar</tt>
|
|
|
|
|
and an <a href="#enhanced">enhanced debugger</a> contained in <tt>smack-debug.jar</tt>.
|
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
<p>
|
|
|
|
@ -56,7 +56,7 @@ Smack uses the following logic to decide the debugger console to use:
|
|
|
|
|
<li>If step 1 fails then Smack will try to use the enhanced debugger. The
|
|
|
|
|
file <tt>smackx-debug.jar</tt> contains the enhanced debugger. Therefore you will need
|
|
|
|
|
to place the jar file in the classpath. For situations where space is an issue you
|
|
|
|
|
may want to only deploy <tt>smack.jar</tt> in which case the enhanced debugger won't be
|
|
|
|
|
may want to only deploy <tt>smack-core.jar</tt> in which case the enhanced debugger won't be
|
|
|
|
|
available.<p>
|
|
|
|
|
|
|
|
|
|
<li>The last option if the previous two steps fail is to use the lite debugger. The lite
|
|
|
|
|