WebSphere Application Server debug limitations

 

Debugging Web objects

 

JSP Debugging:

  • JSP files can be debugged when testing on a WebSphere Application Server. If you are testing on a Tomcat server, the debugger will not stop at JSP breakpoints.

  • Breakpoints can be set in JSP files within the following tags:

    • JSP scriptlets of the form: <% %>

    • JSP expressions of the form: <%= %>

    • JSP declarations of the form: <%! %>

    • jsp:useBean, jsp:getProperty, and jsp:setProperty tags

    • Custom tags

  • Breakpoints cannot be set for the following tag sets:

    • HTML code

    • JSP directives

    • All other standard JSP tags jsp:include, jsp:forward, etc.)

  • If you are migrating a workspace from an older version of WebSphere Studio to this version then you will need to delete your JSP breakpoints and recreate them.

 

Hot Method Replace

  • Changes to source that affect the shape of the class are not supported. This means that changes to method bodies will be hot replaced, while the following are examples of changes that will not be hot replaced:

    • changes to class structure, such as the removal/addition of methods

    • modification of class variables

    • changes to inner classes

  • Changes to the code in the bottom stack frame (the main(...) method) cannot be hot replaced.

  • JSP Debugging does not support hot method replace of Java code.

 

Related concepts

Hot Method Replace for debugging Java applications
Hot Method Replace for debugging applications on WebSphere Application Servers

Related reference
Java and mixed language debug limitations