The Eclipse Java debugger connects to the server where your service runs, allowing you to step through the source code, investigate variables and the stack, just as if you were debugging a local Java class.
You cannot debug services executed with the Dialog Service Test wizard running in the same Eclipse process. The Dialog Service Test wizard does not allow focus to switch to the Java debugger when breakpoints are reached in your Java service implementation.
In addition to using the debugger, you can also add tracing code to the service source. Any output written to System.out is logged in the EAServer log file.
Before beginning the debug process, verify that your Java service compiled successfully and there are no errors.
Send your feedback on this help topic to Sybase Technical Publications: pubs@sybase.com
Your comments will be sent to the technical publications staff at Sybase, Inc. For product-related issues or technical support, contact Sybase Technical Support at 1-800-8SYBASE.