Re: saving a reusing session

I think even I'm confused by all this. Since JSwat 2.0 there has been
built-in help screens. Did you read the one about sessions? That may
help you. In short, session properties are saved automatically. Also
read the help page on classpath. You are probably connecting to a remote
debuggee. In that case, set the sourcepath. Read the docs/help and that
should answer your questions.

This reminds me that I should back-port the help files to 1.5, as
updates to the doc files.

n


On Thu, 2002-06-06 at 12:43, John Gregg wrote:
> Hi all.
> 
> I'm completely baffled by JSwat sessions.  I thought maybe my 1.5.10 version
> was just misbehaving, so I switched to 2.4 but I still don't get it.  Is
> there some documentation I'm missing?
> 
> Here are some things that puzzle me:
> 
> How do I save a session?  There are options to open, copy, and delete
> sessions, but not to save one.  The best I can do is set the current session
> to be how I want and copy it under a new name.
> 
> How do I save classpath info in a session?  Without seeing any docs on the
> subject, my uneducated guess is that a session includes the stuff in the the
> "Start VM" dialog, the classpath, and the source path.  However no matter
> what I do the classpath resets to tools.jar and bootstrap.jar.  Is that by
> design?  Attempting to set the classpath the way I want it, save the
> session, and reopen the session doesn't have the desired effect.  Sometimes
> I even set the classpath, start a session, then go back to tweak the session
> and my earlier changes are gone.  Am I doing this in the wrong order?
> 
> thanks
> 
> john