Re: jsp debugging

The first thing to check is the Default Source Stratum setting in the 
Misc tab of the Preferences dialog. Either make it blank or set it to 
"JSP", that way you get the correct stratum. The original default had 
been "Java" and that would probably explain some of what's going on. 
After version 2.33 the default changed to be blank so the VM default 
stratum is used.

As for the source not found errors, I can't help you unless you give me 
detailed information regarding your sourcepath setting. I need to know 
the exact path to the webapps directory, and what you have put in the 
JSwat "Set Sourcepath" dialog.

You should not set the suppressSmap to true, as that would foil JSwat's 
attempts to locate the .jsp source file. In fact, leave all of the 
Tomcat debugging settings to their default values.

Another thing to try is the 'source' command, which displays all of the 
source-related details of a particular class. This can help you 
determine what the correct sourcepath should be.

And lastly, I have just updated the JSP debugging page on bluemarsh.com, 
so take a look at that if you haven't lately:

    http://www.bluemarsh.com/java/jswat/docs/howto-jsp.html

Thanks for writing and please let us know how it goes.

n


Robert P Young wrote:
> i've attempted both breaking in the jsp file and the generated java
> file.  neither works very well.  in both cases, i get the 'source
> couldn't be found' message.  the class tree is shown, as is locals.
> there is a stop in both cases, but then the process goes into the weeds;
> hard to tell what's happening.  i File/Open File for the generated file,
> but jswat seems to be unaware that it exists.  double clicking the method
> in the class tree gets the source error page.
> 
> loading the jsp as source, gets the green rectangle, a stop, and a source
> error page when stepping.  closing the source error page leaves the jsp
> source with the green rectangle unmoved, and no highlighted line.
> 
> sourcepath includes the work directory to the point above org.apache.....
> and the path to the jsp in the application.  the green rectangle appears
> in both cases, but stepping either goes no where, or the source error
> page.  if i close the source error page when using the generated source
> approach, the next line is highlighted, for a few steps (each time after
> closing the error page).  but then goes into lala land.
> 
> i did the suppressSmap flag.  no difference.
> 
> jswat 2.37/win2k
> java 1.4.2_08
> the server is tomcat 5.0.28
> IE 5.5
> 
> i use both jswat and jdebug.  with the latter, debugging through the
> generated source pretty much works.  for other reasons, i'd rather
> use jswat; so debugging jsp would be useful.
> 
> i found some earlier traffic in the archives, but none which seemed to
> resolve the issue.  has anyone actually debugged jsp with jswat?
> 
> thanks,
> robert
> 860.221.2468