This document lists changes made to the Debugger JPDA APIs. Please ask on the
nbdev@netbeans.org
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.jpda/1 > 1.20
org.netbeans.api.debugger.jpda.JPDADebugger
org.netbeans.api.debugger.jpda.JPDAThread
org.netbeans.api.debugger.jpda.LineBreakpoint
JPDADebugger
; made by: mentlicher; issues:
#67046
A possibility to detect whether the debuggee is read-only is added.
This check works fine on JDK 1.5 and higher, on JDK 1.4 it returns
true
by default.
JPDAThread
; made by: mentlicher; issues:
#59072
A possibility to interrupt a debuggee thread is added.
JPDA API represents JDI functionality. Since JDI interfaces evolve from one version to another, it's necessary to declare that interfaces in org.netbeans.api.debugger.jpda package should not be implemented, since new methods can be added to these interfaces at any time to keep up with the JDI functionality.
Also JPDABreakpointEvent and JPDABreakpointListener are moved to newly created org.netbeans.api.debugger.jpda.event package.
JPDAStep allows to create a step request to JDI with no UI interference. It was designed for new RunIntoMethod action. New method JPDADebugger.createJPDAStep creates a new instance of JPDAStep.
LineBreakpoint
; made by: lkotouc
A line breakpoint does not contain the information about the source path where it is set. There is no way how to differ between breakpoints in the case when - several JSPs have the same name AND - these JSPs are statically included into one JSP page.
This parameter has been added to distinguish between finding sources for smart stepping feature, and for all other features like douuble click on stack trace..
This method is needed to correctly implement fix & continue action.
This method is needed to correctly implement line breakpoint in secondary classes.
ContextProvider.getImports () method added to support better evaluation of expressions. ContextProvider.getLineNumber (annotaion) method added to fix stepping through modified files.
ContextProvider and EngineContextProvider has been changed from interfaces to abstract classes. This was done to support future changes in these classes.
Mew constructor added (InvalidExpressionException(java.lang.Throwable)), and InvalidExpressionException.getTargetException() method added to support firing of nested exceptions.
ContextProvider.getFieldLineNumber() method added.
InvalidExpressionException is fired from folowing methods now:
JPDADebugger.SESSION_ID constant has been added.
We have added several new methods to fix issues in smart stepping implementation:
We have added several new properties to JPDABreakpointEvent:
We have changed ClassLoadUnloadBreakpoint to support class exclusion filters, and more than one class filter. The same change was done for MethodBreakpoints too.
Support for Fix Action improved. Support for Pop Frame action added. Support for static and inherited fields added. New methods:
JPDABreakpointEvent and JPDABreakpointListener classes added. JPDABreakpoint.addJPDABreakpointListener (...) and JPDABreakpoint.removeJPDABreakpointListener (...) methods added.
Methods starting debugger has been modified to support synchronous start of debugging.
Built on May 28 2007. | Portions Copyright 1997-2005 Sun Microsystems, Inc. All rights reserved.