JSwat - Java Debugger

Tracker: Bugs

8 Breakpoints in JSPs in Tomcat not resolving - ID: 2007472

Last Update: Comment added ( nfiedler )

Details:

Dominic Tynes reported that setting breakpoints in his JavaServer Pages
were not resolving (my words). He was using Tomcat 5.5 on Windows (no idea
which version) with an unknown version of JSwat.

Submitted:

Nathan Fiedler ( nfiedler ) - 2008-07-01 07:50

Priority:

Status:

Closed

Resolution:

Works For Me

Assigned:

Nobody/Anonymous

Category:

Features

Group:

v4.x

Visibility:

Public

Comments ( 2 )

Date: 2008-08-14 18:16 Sender: nfiedler Hi Dominic, this issue is also being tracked as a support request, which seems more appropriate to me, pending further details. I cannot reproduce this problem using the latest JSwat (4.3 + local edits), Tomcat 6.0, and JDK 1.6 on Mac OS X. I doubt this is a Windows-only problem, so I'm thinking this must be some configuration issue.
Date: 2008-07-01 20:44 Sender: dominictynes Sorry. Submitted this via the mailing list before I found the bug tracker. Just added a support tracker entry detailing what I have found since then: The problem is caused when the JSP's have <% @include file="XXX/YYY.inx" /> statements in them. If I replace the includes with their respective sources, the debugger works fine. The JSP's and includes are valid, since they compile and run fine in Tomcat and are rendered in a browser. Seems to be an issue with the debugger and include statements? I tried adding the include folder to the sources folders with no luck. This was using latest SUN JDK, Tomcat and JSwat on Windows XP, as of yesterday. Thanks, Dominic

Date: 2008-08-14 18:16
Sender: nfiedler

Hi Dominic, this issue is also being tracked as a support request, which
seems more appropriate to me, pending further details. I cannot reproduce
this problem using the latest JSwat (4.3 + local edits), Tomcat 6.0, and
JDK 1.6 on Mac OS X. I doubt this is a Windows-only problem, so I'm
thinking this must be some configuration issue.

Date: 2008-07-01 20:44
Sender: dominictynes

Sorry. Submitted this via the mailing list before I found the bug
tracker.

Just added a support tracker entry detailing what I have found since
then:
The problem is caused when the JSP's have <% @include file="XXX/YYY.inx"
/>
statements in them.

If I replace the includes with their respective sources, the debugger
works fine.

The JSP's and includes are valid, since they compile and run fine in
Tomcat and are rendered in a browser.

Seems to be an issue with the debugger and include statements? I tried
adding the include folder to the sources folders with no luck.

This was using latest SUN JDK, Tomcat and JSwat on Windows XP, as of
yesterday.

Thanks,
Dominic

Attached File

Changes ( 3 )

Field	Old Value	Date	By
status_id	Open	2008-08-14 18:16	nfiedler
resolution_id	None	2008-08-14 18:16	nfiedler
close_date	-	2008-08-14 18:16	nfiedler

JSwat - Java Debugger

Tracker: Bugs

Comments ( 2 )

Attached File

No Files Currently Attached

Changes ( 3 )

About SourceForge

Find Software

Develop Software

Community

Help