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.
- mount a FS - convert to web module - set the tomcat 32 as default server - create a jsp - compile the jsp - show a servlet - add a servlet breakpoint - a jsp breakpoint automatically generated is pink - compile a JSP - by this time the JSP breakpoint is delete (br.remove()) - debugger.getBreakpoints() -> there is still the JSPServletBreakpoint, but should be deleted - debugger window/breakpoints -> there are still JSP and servlet breakpoint; there should be nothing - servlet line is white, but jsp line is still pink, what is bad
*** Issue 20727 has been marked as a duplicate of this issue. ***
because duplicated bug is P2
another reproduction: When a JSP breakpoint is toggled on, it is added to the list of breakpoints in the Debugger Window. However, when the breakpoint is toggled off, it is not removed from the Debugger Window. If the breakpoint is then toggled back on, a duplicate breakpoint is added to the Debugger Window.
fixed was found and is simple - CoreBreakpoint.getGroup will be public and not protected (debugger core module) - JspCompoundEvent.remove will call myGroup.delete() (web module)
another problems; we will try to find better and safe way, how to get breakpointGroup during jspCompoundEvent.remove
new fix was found: org/netbeans/modules/web/debug/JspCompoundEvent.java > BreakpointGroup bg = getBreakpoint().getGroup(); > if (bg != null) ((BreakpointGroupSupport)bg).delete(); org/netbeans/modules/debugger/BreakpointGroup.java < breakpoint.setGroup (null); --- > // breakpoint.setGroup (null); org/netbeans/modules/debugger/CoreBreakpoint.java < protected BreakpointGroup getGroup () { --- > public BreakpointGroup getGroup () {
Created attachment 4826 [details] changed sources
fixed in main trunk
3.3.2 candidate
*** Issue 21045 has been marked as a duplicate of this issue. ***
integrated into the orion_fcs branch