RE: unable to get to compiled jsp files in debugger

Winner!

Add the following to {catalina_home}/conf/web.xml:

        <init-param>
            <param-name>suppressSmap</param-name>
            <param-value>true</param-value>
        </init-param>   

To the jsp servlet area, on or about line 181

Thanks for the help

Mike

-----Original Message-----
From: Nathan Fiedler [mailto:[email protected]] 
Sent: Friday, May 14, 2004 4:46 PM
To: [email protected]
Cc: [email protected]
Subject: Re: [jswat-user] unable to get to compiled jsp files in
debugger


Another JSwat user found that he had to set the suppressSmap parameter
to 'on' in the conf/web.xml in order to debug JSPs (not sure if he meant
the generated servlets or not). Apparently Tomcat 5.0 changed the manner
in which source code is mapped -- I have not looked into this at all
(this is bug 865).

Try that and see if it helps.

The CPU usage is due to JSwat exhaustively checking every loaded class
for a match to the source file name in order to set the breakpoint. That
is brute force approach used when the parser has failed.

Otherwise, if this is still broken for you, I will have to look into it
sometime. At this point it will be a week or more before I have time.

n