Breakpoint Import Participants



This extension point allows contributors to explicitly define how breakpoints should be compared when being imported into the workspace, and how they should be updated if a similar breakpoint already exists in the workspace.

Configuration Markup:

<!ELEMENT extension (importParticipant)+>

<!ATTLIST extension




<!ELEMENT importParticipant EMPTY>

<!ATTLIST importParticipant

participant CDATA #REQUIRED

type        IDREF #REQUIRED>

Describes one import participant

The following is an example of the breakpoint participant extension:

<extension point="org.eclipse.debug.core.breakpointImportParticipants">

In the above example the participant cares about Java line breakpoints: where org.eclipse.jdt.debug.javaLineBreakpointMarker is a breakpoint type defined using the org.eclipse.debug.core.breakpoints extension point in org.eclipse.jdt.debug

API Information:
The type attribute is the id of the marker backing the breakpoint type this participant cares about. The type needs to be the exact marker id of the breakpoint this participant cares about, marker hierarchies are not considered. For example 'org.eclipse.jdt.debug.javaLineBreakpointMarker', the id of the backing marker for the Java line breakpoint The participant attribute must specify a Java class that implements the org.eclipse.debug.core.model.IBreakpointImportParticipant interface.

Supplied Implementation:
Platform Debug supplies a default implemementation for breakpoints in general which compares breakpoints the way they were compared prior to the participant support: based on breakpoint type and line number information.

Copyright (c) 2008 IBM Corporation and others.
All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at