Overview | Package | Class | Use | Tree | Deprecated | Index | Help
| org.netbeans.api.debugger.jpda/2 2.4.22
PREV NEXT | FRAMES NO FRAMES

# NetBeans Debugger JPDA API

List of APIs: JPDADebuggerAPIJPDA Debugger API JPDADebuggerSPIJPDA Debugger SPI Meta-inf-debugger-netbeans-JPDASession-Java-org.netbeans.spi.debugger.jpda.JPDADebuggerDebugger View loads all model definitions. Meta-inf-debugger-netbeans-JPDASession-org.netbeans.spi.debugger.jpda.JPDADebuggerDebugger View loads all model definitions.

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:

- JPDADebuggerAPIJPDA Debugger API
- JPDADebuggerSPIJPDA Debugger SPI
- Meta-inf-debugger-netbeans-JPDASession-Java-org.netbeans.spi.debugger.jpda.JPDADebuggerDebugger View loads all model definitions.
- Meta-inf-debugger-netbeans-JPDASession-org.netbeans.spi.debugger.jpda.JPDADebuggerDebugger View loads all model definitions.

### What is New (see all changes)?

- Nov 3 '05 Added canBeModified() method to JPDADebugger class

  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.

- Aug 18 '05 Added interrupt method to JPDAThread class

  A possibility to interrupt a debuggee thread is added.

- Aug 12 '05 JPDA API interfaces that correspond to JDI API declared as not to implement.

  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.

- Jun 29 '05 JPDAStep class added (also new method createJPDAStep added to JPDADebugger)

  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.

- Feb 15 '05 LineBreakpoint supplied with the information about the source path where it is set.

  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.

### Use Cases

## UseCase I. - Install and use CPP debugger plug-in to NetBeans + Java Debugger.

CPP debugger plug-in installs support for debugging of some new language to the NetBeans IDE, and some new debugging engine. This implementation of debugger should share UI components (actions, Debugger Views, ...) with default NB Java Debugger. It should share basic debugger model too - notion of current context, current session, thread, call stack line, ...
CPP debugger plug-in installs:

- New set of breakpoint types - CPPLineBreakpointType, CPPMethodBreakpointType...
  - This set of breakpoint types will have special cathegory in Add Breakpoint Dialog called "CPP". Each breakpoint type will install a new JPanel to Add Breakpoint Dialog.
  - ToggleBreakpointAction on CPP files will create / remove a instance of CPPLineBreakpointType.
- Install some watches evaluator for CPP language.
- Some new View to Debugger Window
- Use Termilnal Emulator in Output Window as command line interface to CPP debugger plug-in.
- Install / uninstall a columns to / from standard Debugger Window Views.
- Redefine Nodes used for representation of CPP threads, watches, variables, callstacks, sessions and breakpoints
  - Add / remove some properties
  - Add / remove some actions
  - change icons
  - change display names
- Register CPP Actions for:
  - Step Into, Over, Out, Continue, Pause, Start, Kill, Restart, Finish
- Some new CPP specific actions.

## UseCase II. - Install and use JSP debugger plug-in to NetBeans + Java Debugger.

JSP debugger plug-in installs support for debugging of some new language to the NetBeans Java Debugger. It does not contain a new debugger engine, but it delegates to standard NB Java debugger. So it does not depends on Debugger Core API only, but it depends on JavaDebugger API too.
JSP debugger plug-in installs:

- New set of breakpoint types - JSPLineBreakpointType, ...
  - This set of breakpoint types will have special cathegory in Add Breakpoint Dialog called "JSP". Each breakpoint type will install a new JPanel to Add Breakpoint Dialog.
  - ToggleBreakpointAction on JSP files will create / remove a instance of JSPLineBreakpointType.
  - JSPLineBreakpointType delegates all functionality to JPDAClassBreakpoint and JPDALineBreakpoint
- Some watches evaluator for JSP language expression. This evaluator delegates evaluation of Java expressions to standard JavaExpressionEvaluator.
- Redefine Nodes used for representation of JSP callstacks and breakpoints
  - Add / remove some properties
  - Add / remove some actions
  - change icons
  - change display names
- Register JSP Actions for:
  - Step Into, Over, Out
  - Implementation of this actions delegates to standard Java Step actions - it redefines Java stepping functionality.
- JSP debugger plug in adds support for new programming language (JSP) to already running Java Session.

## UseCase III. - Install and use J2EE debugger plug-in to NetBeans + Java Debugger.

J2EE debugger plug-in installs some enhancements to the standard Java Debugger. It does not contain a new debugger engine or language support. So it does not depends on Debugger Core API only, but it depends on JavaDebugger API too.
J2EE debugger plug-in installs:

- New set of breakpoint types
- Filter for Threads and Callstack Views. This filter should allow to:
  - Add / remove / modify nodes in this views.
- Redefine Stepping (Smart Stepping) behaviour of default Java Debugger.
- Some new View to Debugger Window

## UseCase IV. - Install and use DBX debugger plug-in to NetBeans.

DBX debugger plug-in installs support for debugging of some new language (CPP) to the NetBeans IDE, and some new debugging engine. But it contains debugger engine for Java debugging too. DBX debugger engine has its own session management (or will have in the next versions). One debugger engine can manage more than one sessions. One engine supports debugging in more than one language.

### Exported Interfaces

This table lists all of the module exported APIs with defined stability classifications. It is generated based on answers to questions about the architecture of the module. Read them all...

##### Group of java interfaces

Interface Name | In/Out | Stability | Specified in What Document?
JPDADebuggerAPI | Exported | Official | ../org-netbeans-api-debugger-jpda

##### Group of lookup interfaces

Interface Name | In/Out | Stability | Specified in What Document?

### Implementation Details

##### Where are the sources for the module?

The sources for the module are in NetBeans CVS in debuggerjpda/api directory.

##### What do other modules need to do to declare a dependency on this one?

OpenIDE-Module-Module-Dependencies: org.netbeans.api.debugger.jpda/1

Read more about the implementation in the answers to architecture questions.

Overview | Package | Class | Use | Tree | Deprecated | Index | Help
| org.netbeans.api.debugger.jpda/2 2.4.22
PREV NEXT | FRAMES NO FRAMES

Built on December 7 2006. | Portions Copyright 1997-2005 Sun Microsystems, Inc. All rights reserved.