RE: JSwat forgets classpath arguments

Part of the issue is that in the remote case the classpath comes from
the debuggee, whereas in the launching case, the jswat classpath is
passed to the debuggee. JSwat is not set up to store a remote-only
classpath and a launch-only classpath. There's just the one classpath.
When you attach remotely, the classpath becomes whatever the debuggee's
classpath is set to.

If you or anyone else wants to make a proposal for a change in behavior,
feel free to do so. Make sure to think about both the launching and
remote cases and the fact that each set of named session properties has
a copy of the classpath setting.

BTW, it sounds like maybe you want to set the sourcepath, not the
classpath.

n



> -----Original Message-----
> From: Claes Holmerson [mailto:[email protected]] 
> Sent: Tuesday, September 03, 2002 8:41 AM
> To: [email protected]
> Subject: [jswat-user] JSwat forgets classpath arguments
> 
> Hello,
> 
> I try to use JSwat to debug a servlet application that runs 
> on Tomcat 4. 
> I use remote debugging, and many times when I set the 
> classpath, JSwat 
> forgets about it. This happens when I do "Attach to remote", 
> which greys 
> "Set classpath" out. If I end the session and go back to "Set 
> classpath" 
> my settings has disappeared. When this happens, I can not 
> browse to the 
> class I want to set a breakpoint on, and neither can I set 
> breakpoints 
> in the "Breakpoint tab" (The "Enable button" does not work then). It 
> works sometimes though, which me suspect this is a bug in JSwat. Any 
> ideas? I use JSwat 2.8.
> 
> Regards,
> Claes Holmerson