This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
with glassfish i can see the generated jsp java files in domains/domain1/generated/jsp/j2ee-modules/... after setting the debugger source root to include those .java files i can set breakpoints; when the debugger breaks at a breakpoint -- it does not show me the .java file -- it shows me the .jsp file -- which i dont want so see -- i want to see the java file; the only way i've found around this is to pre-compile the jsp files -- add them as sources to my project, and then modify web.xml to add additional servlets that add/map the class names of the compiled jsp servlets, and also set the paths of the servelts to match the location of the original .jsp files; i may (dont remember) also have to delete/rename the orig .jsp files so the debugging system will not show my breakpoint location within those files -- but instead let me see the java code; there should be an easier way to accomplish this -- but how?
On the JSP file node, there is also the View Servlet action, which shows you the java file generated by GlassFish. Did you try this? Does it help?
i think you mis-understand the issue; view servlet will let me see code; but the debugging is showing me the jsp -- i want the debugging to show me the code -- let me step thru the java jsp code -- not take me to the jsp when i hit a java breakpoint. i debug by attaching to glassfish -- not by using Debug project.
i'm not sure this is an enhancement -- it used to be more friendly for compiled jsp java debugging in previoius releases.
Ok, let's ask Martin Entlicher (who owns Java debugging) about this - Martin, do you know how easy/possible it is to support debugging of the generated Java class? Thanks. Emiddio, what specifically works worse than in previous versions, and which version are you comparing to? Thanks.
ok -- i just experimented with jsp compiled java debugging with nb551 thru nb671; i guess i was wrong; what i find is -- the only way to see the java code of the compiled jsp files in the debugger instead of the debugger showing me the jsp file -- is to modify the web.xml before deployment -- add servlets for each jsp file i want to debug in java and set the path to match the jsp file name; it seems to not matter with nb671 if the java code breakpoint is set in the project or domain1/generated/jsp/deployedName/org/apache/... -- if done in project i have to put the compiled jsp java source code into the project sources -- but i have to have them there anyway to provide a a hook for the web.xml servlets i add. so i guess its an enhancement i would like -- if i set the breakpoint in the jsp file -- show me the jsp file when the breakpoint is hit; if i set the breakpoint in domain1/generated/jsp/deployedName/org/apache/... -- show me that java source file. thanks
in prev comment instead of : domain1/generated/jsp/deployedName/org/apache/... i meant domain1/generated/jsp/j2ee-modules/deployedName/org/apache/...
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss