Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] JSP debugging

Actually, this does help a lot and gives me a few places to explore.

On Thu, Jul 15, 2010 at 3:09 PM, Nitin Dahyabhai <nitind@xxxxxxxxxx> wrote:
> Andrew,
> The server stores the source filename, path, and line number information
> into the SMAP when it translates the jsp/gsp into Servlet source and
> compiles the .class file.  JDT and our plug-ins aren't involved with this
> part. The debugger doesn't actually need the .class files since the JDI
> stack frame communicates the class' source filename and path information
> based on the SMAP.  When it comes to the path value, however, we're at the
> mercy of the server's translation engine as the path is underspecified in
> the JSR (see bug 99674 for the gory details).  The launch's source lookup
> director will still try to find the right file in the launch's projects
> based on this information.
> Basically I think your biggest concern will actually be setting and
> clearing Java Stratum breakpoints with class values that "hit"
> consistently and path values that work for the source lookup.  Being able
> to use the Display/Execute/Inspect abilities that are available in the
> Java editor would be fantastic, but we haven't explored those features
> ourselves, yet.

Back to the top