- This topic has 3 replies, 2 voices, and was last updated 21 years, 2 months ago by
.
-
Posts
-
Hi Support team:
Since my jsp debugging is now on hold I was wondering if there was a way to step into the actual servlet code (set breakpoints there) instead of the actual jsp source.
I used to do this in my assembler/C development days when I was doing debugging on the assembler level. (That dates me!)
If I could see the actual servlet code that the jsp is compiled into and set breaks there that would be sufficient for me.
Also, a second question….
I would like to have myeclipse break on ANY exception. I can’t seem to set this with the gui. It always selects one of the many exceptions in the list. I tried using * as the documentation suggested but whatever exception was highlighted in the list box would be set.
Thanks,
EdEd,
Since my jsp debugging is now on hold I was wondering if there was a way to step into the actual servlet code (set breakpoints there) instead of the actual jsp source.
I used to do this in my assembler/C development days when I was doing debugging on the assembler level. (That dates me!)
If I could see the actual servlet code that the jsp is compiled into and set breaks there that would be sufficient for me.
I remember doing the same thing, but it was breakpoints in the C code generated by CFront. Anyway, currently we only directly support source level debugging of JSP’s in JSR-045 compliant containers. But, you could precompile your JSP’s into java and then import the java source into a source folder in the appropriate package of your Eclipse projects. Once you’ve done that, the debugger should find the java source fine.
I would like to have myeclipse break on ANY exception.
To do this, just set a breakpoint on Throwable since all exceptions and errors extend it.
