|
org.netbeans.api.debugger.jpda/2 2.4.22 | |||||||||
PREV NEXT | FRAMES NO FRAMES |
See:
Description
Debugger JPDA API | |
---|---|
org.netbeans.api.debugger.jpda | JPDA Debugger APIs provide representation of JDI functionality. |
org.netbeans.api.debugger.jpda.event | |
org.netbeans.spi.debugger.jpda | JPDA Debugger SPIs defines support for Smart Stepping, Variables Filterring and filterring of all Debugger Views. |
List of APIs:
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.
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.
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.
|
|
The sources for the module are in NetBeans CVS in debuggerjpda/api directory.
Read more about the implementation in the answers to architecture questions.
|
org.netbeans.api.debugger.jpda/2 2.4.22 | |||||||||
PREV NEXT | FRAMES NO FRAMES |