- This topic has 3 replies, 2 voices, and was last updated 21 years ago by
.
-
Posts
-
I have a webapp which produces an exception. I run it in Tomcat 5 under MyEclipse control. I surf to the *.jsp that does this. The browser shows me a nice stacktrace.
But there is no trace of that stacktrace to be seen in Eclipse!
I expected that I could just click on a filename/linenumber somewhere to see which code caused the exception.
So I vaguely remembered the “breakpoint on exception” feature from Eclipse, so I set a breakpoint on ServletException. This kinda works — the debugger does kick in. But I can’t find the line in my code anyway, because the exception it shows me is not the “root cause”.
What do I do?
An example webapp can be found under http://www.emptydomain.de/kai/taglibtest.zip. I just zipped up the corresponding subdir of my Eclipse 3.0M4 workspace. Surf to the *.jsp file included there.
tia,
KaiKai,
It appears that your domain isn’t available for downloading the zip. Since you’re using Tomcat 5, can you just set a few breakpoints in your JSP page and then step through it until the exception is thrown?
–Scott
MyEclipse Support> [The zip file can’t be downloaded]
I just tried from the company, and now it works. Hm.
http://www.emptydomain.de/kai/taglibtest.zip
Ah! Clicking on the link in my post doesn’t work because of the trailing dot. Sorry.> [Set breakpoint in JSP and step]
Of course I can do that, but I’m so *lazy* 😉 Don’t get me wrong: I’m quite happy with the product. It’s just that when I taste something good, I want more. Also, I thought I might have missed a simple button or menu item somewhere.
Thank you for such a wonderful product.
Kai
Kai,
Of course I can do that, but I’m so *lazy* 😉 Don’t get me wrong: I’m quite happy with the product. It’s just that when I taste something good, I want more. Also, I thought I might have missed a simple button or menu item somewhere.
Thank you for such a wonderful product.I certainly understand and thanks for the kudos on the product. We’re working on some big additions for the next two months so it will only get better. As far as ‘missing a button’ or something. You haven’t; you’ve just found the current limits of the debugging support. I’ve entered an enhancement request for the issue you mentioned.
–Scott
MyEclipse Support
