Rational Developer for i
7.5.0

com.ibm.etools.systems.app.model.bin.impl
Class BoundRelationshipImpl

java.lang.Object
  extended by EObjectImpl
      extended by com.ibm.etools.systems.app.model.impl.RelationshipImpl
          extended by com.ibm.etools.systems.app.model.bin.impl.BoundRelationshipImpl
All Implemented Interfaces:
BoundRelationship, Relationship

public class BoundRelationshipImpl
extends RelationshipImpl
implements BoundRelationship

An implementation of the model object 'Bound Relationship'.


Field Summary
static String copyright
           
 
Fields inherited from class com.ibm.etools.systems.app.model.impl.RelationshipImpl
source, subtype, SUBTYPE_EDEFAULT, target, type, TYPE_EDEFAULT
 
Constructor Summary
protected BoundRelationshipImpl()
           
 
Method Summary
protected  EClass eStaticClass()
           
 
Methods inherited from class com.ibm.etools.systems.app.model.impl.RelationshipImpl
basicGetSource, basicGetTarget, eGet, eIsSet, eSet, eUnset, getSource, getSubtype, getTarget, getType, setSource, setSubtype, setTarget, setType, toString
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
 
Methods inherited from interface com.ibm.etools.systems.app.model.Relationship
getSource, getSubtype, getTarget, getType, setSource, setSubtype, setTarget, setType
 

Field Detail

copyright

public static final String copyright

See Also:
Constant Field Values
Constructor Detail

BoundRelationshipImpl

protected BoundRelationshipImpl()

Method Detail

eStaticClass

protected EClass eStaticClass()

Overrides:
eStaticClass in class RelationshipImpl

Rational Developer for i
7.5.0

Copyright 2009 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.