Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Web Tools Project (WTP) » How to obtain original line numbers for exceptions in JSPs?
How to obtain original line numbers for exceptions in JSPs? [message #185007] Fri, 15 December 2006 10:11 Go to next message
Michael Moser is currently offline Michael Moser
Messages: 914
Registered: July 2009
Senior Member
I am trying to debug a JSP that throws a null pointer exception. The
line number that's reported is the one in the generated .java code and
has no meaning for the jsp. Where does Geronimo put those temporary
files, so that I can peek into those to figure out, which line in my
original .jsp file causes this?

Or how else does one debug this? I tried and started the server
(Geronimo 1.1) in debug mode obviously that doesn't catch this
exception.

Michael
Re: How to obtain original line numbers for exceptions in JSPs? [message #185226 is a reply to message #185007] Tue, 19 December 2006 08:53 Go to previous messageGo to next message
Eclipse User
Originally posted by: dserodio.gmail.com

Michael Moser wrote:
> I am trying to debug a JSP that throws a null pointer exception. The
> line number that's reported is the one in the generated .java code and
> has no meaning for the jsp. Where does Geronimo put those temporary
> files, so that I can peek into those to figure out, which line in my
> original .jsp file causes this?

If you're using Geronimo + Tomcat, it should be under a "work/"
directory somewhere inside the Geronimo installation (under catalina/ or
something like that).

HTH,
Daniel Serodio
Re: How to obtain original line numbers for exceptions in JSPs? [message #185464 is a reply to message #185007] Fri, 29 December 2006 20:21 Go to previous message
David Williams is currently offline David Williams
Messages: 696
Registered: July 2009
Senior Member
On Fri, 15 Dec 2006 10:11:43 -0500, Michael Moser <mmo@zurich.ibm.com>
wrote:

> Or how else does one debug this?


Don't forget, you can use all the normal debug facilities, such as setting
breakpoints,
etc, in the JSP, including setting Java Exception breakpoints ... but, as
with most Java,
NullPointerExceptions are sometimes common, so you'll sometimes hit many
of these
before hitting the unexpected one. This can be helped somewhat by setting
a breakpoint
near the beginning of your JSP, and once you hit it, _then_ turn on the
NPE breakpoint.
Previous Topic:NoClassDefFoundError when deploying with
Next Topic:No J2EE perspective, no Dynamic web project
Goto Forum:
  


Current Time: Sun Aug 31 00:37:48 EDT 2014

Powered by FUDForum. Page generated in 0.13894 seconds