[Scott Anderson]

Tomcat 5 has full support for JSR-045 and so does MyEclipse 2.1.1 EA2 and later. You don’t need to do anything special to enable debugging on Tomcat 5, just deploy your web app, set your breakpoints, and invoke your JSP pages.

For earlier versions of Tomcat, I’d suggest developing on Tomcat 5 and deploying on the earlier releases for production to get a nice mix of developer ease and production reliability.

–Scott
MyEclipse Support

[Panagiotis Korros]

how can i set a break point in a jsp page?

[Scott Anderson]

Basically, just like you do on a Java class:
1) Open the JSP page with the MyEclipse JSP editor (It has to be our editor)
2) Double-click in the left margin on the page, next to the line of Java where you’d like the breakpoint.
3) The standard circular, blue marker will be drawn.

When you execute the page within Tomcat 5, the code will be loaded so the breakpoint will be redrawn to include a check mark and when the line is hit you’ll be sent to the debug perspective, if that’s how you have your Eclipse preferences set.

–Scott
MyEclipse Support

[AllenConquest]

I now have JSP debugging in Tomcat 5 working. But I use a lot of JSTL/Struts tags, and it seems that the debugger can’t handle these. Just a simple Struts JSP file starting with <html:html> stops the debugger getting to any breakpoints within this tag. Is there a way round this, or is it a known problem with debugging tags ?

Thanks,

Allen

[Riyad Kalla]

Allen,
We have seen this behavior and are looking into it. However it is behind a few top-priority items for MyEclipse 2.8 so we may not find a resolution immediately.

[AllenConquest]

Thanks for responding so promptly. I look forward to trying 2.8 and hope that you can take a look at this soon. Apart from this little glitch MyEclipse is a fantastic addon to Eclipse and make developing so much easier.

Keep up the good work!!

[Author]

Posts