org.netbeans.api.debugger/1 1.42

Debugger Core API
Official

The Debugger Core API module defines common structures for integration of debugger implementations into NetBeans IDE.

See: Description

Debugger Core API 
Package Description
org.netbeans.api.debugger
The NetBeans Debugger Core API definition.
org.netbeans.spi.debugger
The NetBeans Debugger SPI definition defines interface to Debugger Plug-ins.

The Debugger Core API module defines common structures for integration of debugger implementations into NetBeans IDE.
List of APIs:

Registrations in standard Lookup:

What is New (see all changes)?

  • Mar 27 '12 API for changing enabled state of a Watch

    Two method are added to Watch class: isEnabled() and setEnabled(boolean). When the enabled state changes, PROP_ENABLED event is fired.

  • Dec 19 '11 Added a possibility to enable/disable other breakpoints when one is hit.

    Four methods are added to the Breakpoint class, that allow to get or set a set of breakpoints, that are enabled or disabled when the breakpoint is hit. One test method is provided, which determines if the dependent breakpoints are supported by the implementation.

    Added methods:
    Breakpoint.canHaveDependentBreakpoints(), Breakpoint.getBreakpointsToEnable(), Breakpoint.setBreakpointsToEnable(), Breakpoint.getBreakpointsToDisable(), Breakpoint.setBreakpointsToDisable().

  • Nov 12 '10 Evaluate action is made generic, based on action providers.

    Evaluate action is moved from JPDA Debugger into Debugger Core UI module. ActionsManager.ACTION_EVALUATE constant was added for use by debugger-specific provider (ActionsProvider) of Evaluate action.

  • Sep 10 '10 Allow multiple debugger service registrations and position order

    Allow to specify the order of the debugger service registry. For the need of being able to define multiple different registrations for a single instance, @DebuggerServiceRegistrations and ActionsProvider.Registrations annotations are introduced.

  • Feb 28 '10 Breakpoints group properties.

    Add Breakpoint.getGroupProperties() method, that returns an implementation of GroupProperties class with the relevant grouping information used by BreakpointsWindow to create hierarchy of breakpoint groups

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.

UseCase V. - Implement Debugger Core UI module on top of Debugger Core API / SPI.

Debugger Core UI needs:
  • List all breakpoint types and all breakpoint cathegories.
  • Visually customize all breakpoints - some panel.
  • Add / remove breakpoints.
  • Add / remove watches.
  • Represent breakpoints, threads, thread groups, watches, sessions, call stack frames, locales, and fields as Nodes in NB Explorer View.
  • List all threads, thread groups, locales, watches, breakpoints, callstack frames, and fields.
  • Listen on changes of hierarchy of threads, thread groups, locales, watches, breakpoints, callstack frames, and fields.
  • Some current context definition. Current contet should define current session, language, thread, and call stack line.

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 NameIn/OutStabilitySpecified in What Document?
DebuggerCoreAPIExportedOfficial../org-netbeans-api-debugger

Group of lookup interfaces
Interface NameIn/OutStabilitySpecified in What Document?

Group of property interfaces
Interface NameIn/OutStabilitySpecified in What Document?

Implementation Details

Where are the sources for the module?

The sources for the module are in the NetBeans Mercurial repositories.

What do other modules need to do to declare a dependency on this one, in addition to or instead of a plain module dependency?
Nothing.

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

org.netbeans.api.debugger/1 1.42

Built on May 21 2013.  |  Portions Copyright 1997-2013 Oracle. All rights reserved.