Rational Developer for Power Systems Software
V7.6

com.ibm.etools.systems.app.model.src
Interface InvokesRelationship

All Superinterfaces:
Relationship
All Known Implementing Classes:
InvokesRelationshipImpl

public interface InvokesRelationship
extends Relationship

A representation of the model object 'Invokes Relationship'. Inovokes relationship between two CallableBlocks representing that the source CallableBlock invokes the target CallalbeBlock from sourcePosition.

The following features are supported:

See Also:
SrcPackage.getInvokesRelationship()

Field Summary
static String copyright
           
 
Method Summary
 int getSourcePosition()
          Returns the value of the 'Source Position' attribute.
 void setSourcePosition(int value)
          Sets the value of the 'Source Position' attribute.
 
Methods inherited from interface com.ibm.etools.systems.app.model.Relationship
getSource, getSubtype, getTarget, getType, setSource, setSubtype, setTarget, setType
 

Field Detail

copyright

static final String copyright

See Also:
Constant Field Values
Method Detail

getSourcePosition

int getSourcePosition()
Returns the value of the 'Source Position' attribute.

If the meaning of the 'Source Position' attribute isn't clear, there really should be more of a description here...

Returns:
the value of the 'Source Position' attribute.
See Also:
setSourcePosition(int), SrcPackage.getInvokesRelationship_SourcePosition()

setSourcePosition

void setSourcePosition(int value)
Sets the value of the 'Source Position' attribute.

Parameters:
value - the new value of the 'Source Position' attribute.
See Also:
getSourcePosition()

Rational Developer for Power Systems Software
V7.6

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.