New/Edit Breakpoint - Definition

Use to specify the definition of the breakpoint.

Breakpoint Type

Choose the type of breakpoint you want to create. If you are editing an existing breakpoint, the type of the existing breakpoint will be displayed, but you cannot change it.

Source: Breakpoint for a specific line of source code. Source breakpoint icons appear in the margin of the source editor. A source breakpoint can be created by clicking the line number in the source editor or by choosing New Breakpoint from the context menu in the Breakpoints Window.
Exception: Breakpoint for a specific exception class. The breakpoint will occur when an exception is thrown.; Note: The JDeveloper debugger automatically creates a persistent exception breakpoint for uncaught throws for java.lang.Throwable; this breakpoint will occur whenever an uncaught exception is thrown. You cannot delete a persistent breakpoint.
Deadlock: Breakpoint for a monitor block cycle deadlock. Not all Java Virtual Machines support deadlock detection; for example, the HotSpot VM does not support deadlock detection.; Note: The JDeveloper debugger automatically creates a persistent deadlock breakpoint; this breakpoint will occur whenever a monitor block cycle is detected. You cannot delete a persistent breakpoint. You cannot create a new deadlock breakpoint, but you can edit the existing persistent deadlock breakpoint.
Method: Breakpoint for a method. The breakpoint will occur when the specified method is executed.
Class: Breakpoint for a class. The breakpoint will occur when any method in the specified class is executed, just as if a source breakpoint has been placed at the first line of each method in the class.

Source Breakpoint Details

Package: Specify the package for the source breakpoint. For example, java.util.
Source File: Specify the source file for the source breakpoint. The source file specified here should not contain any directory information, but should contain the filename extension. For example, Vector.java.
Line Number: Enter the line number for the source breakpoint.

Exception Breakpoint Details

Exception Class: Enter the fully qualified name for the exception. If you are debugging PL/SQL and would like to create an exception breakpoint for a particular Oracle error code, enter the following for the name of the exception: Oracle.EXCEPTION_ORA_
: For example, $Oracle.EXCEPTION_ORA_6502
Break For Caught Exceptions (selected by default): Select if you want the debugger to stop if the exception will be caught.
Break For Uncaught Exceptions: Select if you want the debugger to stop if the exception will not be caught.

Method Breakpoint Details

Method Name: Enter the fully qualified method name.; For example: java.util.ArrayList.size

Class Breakpoint Details

Class Name Enter the fully qualified name for the class.

Breakpoint Group Name: Enter the name of the breakpoint group to which you would like this breakpoint to belong.

Putting a breakpoint into a breakpoint group is useful for the following reasons:

You can set a breakpoint's actions so that when the breakpoint occurs, it enables or disables all the breakpoints in a specific breakpoint group.
You can edit a breakpoint group so that each breakpoint in the group has the exact same conditions and actions.
In the Breakpoints window, you can quickly enable, disable, or remove, all the breakpoints belonging to a specific breakpoint group.
In the Breakpoints window, you can expand or collapse breakpoint groups so that you can focus your attention on specific breakpoints while ignoring others.

Breakpoints belonging to a breakpoint group are displayed in the Breakpoints window as child nodes of the breakpoint group's parent node.