Community
Participate
Working Groups
- define an app server, e.g JBoss - create a dynamic web ptoject with a JSP - Open JSP with JSP editor and set break point - debug the app server and launch browser point to the URL for the JSP - Eclipse breaks into the JSP. But the code line is not highligted as it should be as in the Java code editor. A little bit more research shows that JSP editor may not handle the IP annotation correctly. * try create a simple Java app with a main() method. let JDT debugger to break in a java line Mouse over the annotation marker in the left side vertical bar: In Java Editor, the message shows: "Multiple markers at this line - Line breakpoint:TestMain [line: 6] - main(String[]) - Debug Current Instruction Pointer" * while in JSP editor, second marker was missing: " - Debug Current Instruction Pointer"
Is the correct file actually open? We're currently unable to set a universally correct path as well as the source file name, so it's possible that the source locator is opening a different file than the one where the breakpoint marker is actually set.
The behavior is AFTER I manually configured the Source Path Lookup and the correct JSP is openned by JSP Editor.
For one thing I'm not sure why you'd have to manually configure the source lookup path--the server configuration should have already set it up for you. But again I'm curious if the file you've gotten it to open is the *exact* resource where you set the breakpoint.
I switched to a new workspace and created a new project with a single index.jsp. This is the only file that can be openned so it must be the right one. You are right I don't need setup source lookup path for JSP since it is already setup in Launch configuration. I did it when select to see the generated JSP servlet source code index_jsp.java.
Verified on M7 that it uses the "Debug Current Instruction Pointer" annotation display preferences, courtesy of our new syntax coloring scheme.
