This document lists changes made to the Debugger Core APIs. Please ask on the
mailing list if you have any questions about the details of a
change, or are wondering how to convert existing code to be compatible.
Fuller descriptions of all changes can be found below (follow links).
Not all deprecations are listed here, assuming that the deprecated APIs continue to essentially work. For a full deprecation list, please consult the Javadoc.
These API specification versions may be used to indicate that a module requires a certain API feature in order to function. For example, if you see here a feature you need which is labelled 1.20, your manifest should contain in its main attributes the line:
OpenIDE-Module-Module-Dependencies: org.netbeans.api.debugger/1 > 1.20
To be able to set breakpoint for number of iterations, we need to add a filter for hit counts into Breakpoint API.
This constant is used in property change events as a notification about change in validity.
Breakpoint.VALIDITY - enumeration of constants for breakpoint validity.
Breakpoint.setValidity() - validity management.
This constant is used in action performer which implements an operation step.
These can be used to call and implement asynchronous actions.
Having final modifier for this method can be too obstructive in some cases. I had a problem writing tests.
Breakpoint.getGroupName (), Breakpoint.setGroupName () methods were added. Breakpoint.PROP_GROUP_NAME has been added.
ActionsProvider.doAction (...) and
ActionsManagerListener.actionPefrormed (...) methods
will not return boolean any longer. This parameter was unusefull and it was not posible to
implement it in some meaningful way.
void DebuggerManager.startDebugging (DebuggerInfo) has been changed to
DebuggerManager.startDebugging (DebuggerInfo). So it returns array of all DebuggerEngines
created for given DebuggerInfo.
Built on January 29 2008. | Portions Copyright 1997-2007 Sun Microsystems, Inc. All rights reserved.