jsp debugging

Robert P Young <[email protected]> Wed, 27 Jul 2005 15:53:46 -0400
Newsgroups gmane.comp.java.jswat.user
Message-ID <OF045FA3EC.8F3547FA-ON8525704B.006AAFBD-8525704B.006D4AE7@csc.com>



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

I particularly dislike classes with a lot of get and set functions.
-- Bjarne Stroustrup/Oct 2003


----------------------------------------------------------------------------------------

This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
----------------------------------------------------------------------------------------