diff --git a/documentation/debugging.html b/documentation/debugging.html index b96a83602..03aab3cec 100644 --- a/documentation/debugging.html +++ b/documentation/debugging.html @@ -48,13 +48,12 @@ Smack uses the following logic to decide the debugger console to use:
  1. It will first try use the debugger class specified in the Java system property - smack.debuggerClass. This is a good place if you want to hook your own - debugger console. If you need to develop your own debugger all you need to do is + smack.debuggerClass. If you need to develop your own debugger, implement the SmackDebugger interface and then set the system property on the command line such as:

    java -Dsmack.debuggerClass=my.company.com.MyDebugger SomeApp

    -

  2. If step 1 fails then the next option is to try to use the enhanced debugger. The +
  3. If step 1 fails then Smack will try to use the enhanced debugger. The file smackx-debug.jar 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 smack.jar in which case the enhanced debugger won't be @@ -68,11 +67,11 @@ Smack uses the following logic to decide the debugger console to use: Enhanced Debugger

    +Full Debug Window + When debugging mode is enabled, a debug window will appear containing tabs for each new created connection. The window will contain the following information: - - +
    +

    Lite Debugger

    +Lite Debug Window + When debugging mode is enabled, a debug window will appear when each new connection is created. The window will contain the following information: - - -