Re: Remote Applet Debugging

It sounds like the remote applet part is not important here, but instead 
it is a question of setting the sourcepath. See the help topic titled 
"Classpath and Sourcepath", which describes how JSwat locates source 
code. Unfortunately, you don't find out how to set the sourcepath until 
you get to the Troubleshooting section. I'll have to correct that. In 
any case, you set the sourcepath in the Session Settings dialog (Session 
menu, Settings item), using the path editor in the "Sources" tab.

Once JSwat knows where to look for your source code, it will display the 
source whenever a breakpoint is hit, or while single-stepping.

n


Flatoff Allan wrote:
> Hello,
> 
> I have attempted to debug an applet with Jswat (unsuccessfully) and 
> here's the result.
> 
> Maybe someone can help . . .
> 
> Some background:
> 
> I can't launch the applet using appletviewer since the applet can't run 
> standalone.  It uses
> getBaseUrl to obtain the Applet's address which it in turn uses to call 
> a servlet which accesses
> Items in the user's web session.  - So basically no web session - no 
> running my applet
> 
> ___http://java.sun.com/j2se/1.4.2/docs/api/java/applet/Applet.html#getCodeBase()_ 
> 
> 
> So therefore I have to run the debugger remotely.
> 
> I followed the instructions here:
> 
> ___http://www.bluemarsh.com/java/jswat/docs/howto-applet.html_
> 
> And in the Jswat online help to get connected to the session.
> 
> I managed to get a debug session going -
> 
> Here's my question:
> 
> How do I get to see my applet source code and set break points?
> 
> Obviously I will have to view a decompiled version of it or something -
> Since applets are compiled class files
> 
> I'll keep trying at it but if anyone can point me in the right direction 
> it would be appreciated.
> 
> Thanks!