Re: jsp questions

1. Not necessarily. All the 'jpda' flag does is enable the debugger to 
connect to Tomcat. To compile JSPs for debugging, take a look at the 
conf/web.xml file -- it contains explanations for every setting, even 
the ones about debugging.

2. What do you mean by "can't see any values"?

3. No, you can debug both servlets and JSPs quite easily by setting the 
"Default Source Stratum" to blank. Yes, JSPs are turned into servlets, 
but you are not interesting in debugging the generated code, I assume, 
so leave the stratum set to blank.

I will make an attempt to reword the howto-jsp.html to make it more 
clear about the stratum setting. If you notice anything else that is not 
entirely clear, please let me know.

Connecting via sockets or shared memory makes little difference, 
although in the past I noticed stability problems with shared memory, 
but that seems to have been cleared up in JDK 1.5.

Thanks

n


[email protected] wrote:
> Hi,
> 
> I am new to JSWAT and have a couple of questions.
> 
> 1)  Does running Tomcat with "catalina.bat jpda start" force the jsp 
> pages to be compiled in debug mode?
> 2)  If 1) is true, when I deploy my war file, I can't just open the 
> directory, I have to open an individual jsp page, set a break point and 
> that seems to work, however I can't see any values, am doing something 
> wrong with the classpath for the java types?  (probably confused myself 
> here).
> 3)  If I read correctly, you can't debug jsp and servlets at the same 
> time, I would need to set up two sessions?  If this is true, are not JSP 
> pages actually servlets at the end of the day?
> 
> If someone has wrote a more thorough introduction with 
> jsp/servlets/tomcat (war files), I would like to see it.  
> 
> Thanks for the help, Swat is pretty neat from what I have seen so far.  
> 
> Ron
> 
> PS.  If it matters I am connected with a port and not shared memory (I 
> assume the end result is the same)