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.

Bug 33435 - Both breakpoint-remove & breakpoint-disable calls the same method.
Summary: Both breakpoint-remove & breakpoint-disable calls the same method.
Status: CLOSED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: All All
: P1 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-06 16:51 UTC by Jan Jancura
Modified: 2010-04-29 09:13 UTC (History)
2 users (show)

See Also:
Issue Type: TASK
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Jancura 2003-05-06 16:51:18 UTC 
This is problem for some debugger plug-ins. 

Method:
CoreBreakpoint.Event.remove ().
Comment 1 Jan Jancura 2003-05-06 17:03:43 UTC 
We should find some quick fix for nb3.5.x branch and separate issue
should be created for long term solution in nb 4.0.
Comment 2 Jan Jancura 2003-06-25 15:03:07 UTC 
I was thinking about this issue, and I see two solutions:
1) I can implement some (not a big) redesign of debugger APIs. And
create two separate methods in Breakpoint.Event for disable and remove.
2) We can use current solution with one method, and do some state
testing in method implementation.

I strongly prefer the solution 2). Redesign can be dangerows/ buggy.
So, how to do it.
for "remove" stuff - just implement the code in Event.dispose
method(). This method is called when breakpoint is removed (=deleted)
only.

and for "disable" code use this:

DBXBreakpointEvent.remove () {
  if (!getBreakpoint ().isEnabled ()) {
    // put "disable" handler code here 
    
  }
}

Is it good solution for you?
(feel free to reopen this issue, if it is not)
Comment 3 Quality Engineering 2010-04-29 09:13:17 UTC 
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.