facebook

JSP Break Point not working unless on the first line

  1. MyEclipse IDE
  2.  > 
  3. General Development
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #200091 Reply

    ldoud
    Member

    JDK: 1.4.2_02
    Tomcat: 5.0.14
    Eclipse: 2.1.1
    MyEclipse: 2.6.4

    In the following JSP I can put a break point on “Hello World” and execution stops correctly. If I put the break point on “Another piece of text.” it skips right by.

    Hello World

    <% request.setAttribute(“foo”, “foovalue”); %>

    Another piece of text.

    #200097 Reply

    support-michael
    Keymaster

    At this time JSP breakpoints are tailored for suspending execution within scriptlet and expression code. So when you say breakpoints on another line get passed by do you mean something like this or it another scenario?

    <% request.setAttribute(“foo”, “foovalue”); %>
    <table> <!– break point here –>

    </table>

    Michael
    MyEclipse Support

    #200106 Reply

    ldoud
    Member

    Yes and no. The first break point I set on a line of HTML and it does stop execution. The second break point is set on the second line of HTML and execution skips on by.

    So for now break points only work on scriplets and expression code? I’m not sure what you mean by expression code. I’m familiar with JSTL and the EL it uses. Is expression code a new EL feature in JSP 2.0?

    Will break points stop execution on custom tag libraries? For example can I put a break point on a <c:if> or a <c:forEach> and expect execution to stop?

    #200108 Reply

    support-michael
    Keymaster

    Will break points stop execution on custom tag libraries? For example can I put a break point on a <c:if> or a <c:forEach> and expect execution to stop?

    In Tomcat5 breakpoints will suspend execution at the point in which they are set. The issue at present is that the Eclipse 2.1.x debug model is closed and does not support filtering and translation at a low-level. So the default MyEclipse behavior is invoke that results in display of the taglib’s java source code. Since it is not available by default you will get the default code display view presenting the methods of the class with no source.

    The Eclipse 3.0 debug revision and new features provides us more opportunitity to do some really nice new levels of debugging. We’ll have more to say about this in the next few months.

    Michael
    MyEclipse Support

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: JSP Break Point not working unless on the first line

You must be logged in to post in the forum log in