com.ibm.etools.systems.application.visual.editor.srcinfo.editpolicies
Class ConnectionEditPolicy
java.lang.Object
OpenEditPolicy
com.ibm.etools.systems.application.visual.editor.srcinfo.editpolicies.ConnectionEditPolicy
- Direct Known Subclasses:
- CallsConnectionEditPolicy, IncludesConnectionEditPolicy, InvokesConnectionEditPolicy
public class ConnectionEditPolicy
- extends OpenEditPolicy
Default edit policy for a source connection. Subclasses can override the getLineNumber method
to allow for positioning to a specific line when the editor opens.
Method Summary |
protected ConnectionEditCommand |
getEditCommand(Command editCommand,
int lineNumber)
Subclasses can override to return their own edit command. |
protected int |
getLineNumber(EObject element)
Subclasses can override to have the editor positioned to a specific line when
the source for this connection is opened. |
protected Command |
getOpenCommand(Request request)
|
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
copyright
public static final String copyright
- See Also:
- Constant Field Values
ConnectionEditPolicy
public ConnectionEditPolicy()
getOpenCommand
protected Command getOpenCommand(Request request)
getLineNumber
protected int getLineNumber(EObject element)
- Subclasses can override to have the editor positioned to a specific line when
the source for this connection is opened.
- Parameters:
element
- EMF model element for source of the connection.
getEditCommand
protected ConnectionEditCommand getEditCommand(Command editCommand,
int lineNumber)
- Subclasses can override to return their own edit command.
Copyright © 2011 IBM Corp. All Rights Reserved.
Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.