Rational Developer for i
7.5.0

com.ibm.etools.systems.app.model.bin
Interface BoundModule

All Superinterfaces:
Artifact, IDebuggable
All Known Implementing Classes:
BoundModuleImpl

public interface BoundModule
extends Artifact, IDebuggable

A representation of the model object 'Bound Module'.

The following features are supported:

See Also:
BinPackage.getBoundModule()

Field Summary
static String copyright
           
 
Method Summary
 BinaryArtifact getBinaryContainer()
          Returns the value of the 'Binary Container' container reference.
 EList getCallableBlocks()
          Returns the value of the 'Callable Blocks' containment reference list.
 SourceContainer getSourceContainer()
          Returns the value of the 'Source Container' reference.
 boolean isDebuggable()
          Returns the value of the 'Debuggable' attribute.
 void setBinaryContainer(BinaryArtifact value)
          Sets the value of the 'Binary Container' container reference.
 void setDebuggable(boolean value)
          Sets the value of the 'Debuggable' attribute.
 void setSourceContainer(SourceContainer value)
          Sets the value of the 'Source Container' reference.
 
Methods inherited from interface com.ibm.etools.systems.app.model.Artifact
getLocation, getName, getSubtype, getType, getVersion, isExternal, setExternal, setLocation, setName, setSubtype, setType, setVersion
 

Field Detail

copyright

static final String copyright

See Also:
Constant Field Values
Method Detail

getBinaryContainer

BinaryArtifact getBinaryContainer()
Returns the value of the 'Binary Container' container reference. It is bidirectional and its opposite is 'Modules'.

If the meaning of the 'Binary Container' container reference isn't clear, there really should be more of a description here...

Returns:
the value of the 'Binary Container' container reference.
See Also:
setBinaryContainer(BinaryArtifact), BinPackage.getBoundModule_BinaryContainer(), BinaryArtifact.getModules()

setBinaryContainer

void setBinaryContainer(BinaryArtifact value)
Sets the value of the 'Binary Container' container reference.

Parameters:
value - the new value of the 'Binary Container' container reference.
See Also:
getBinaryContainer()

getSourceContainer

SourceContainer getSourceContainer()
Returns the value of the 'Source Container' reference.

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

Returns:
the value of the 'Source Container' reference.
See Also:
setSourceContainer(SourceContainer), BinPackage.getBoundModule_SourceContainer()

setSourceContainer

void setSourceContainer(SourceContainer value)
Sets the value of the 'Source Container' reference.

Parameters:
value - the new value of the 'Source Container' reference.
See Also:
getSourceContainer()

isDebuggable

boolean isDebuggable()
Returns the value of the 'Debuggable' attribute.

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

Specified by:
isDebuggable in interface IDebuggable
Returns:
the value of the 'Debuggable' attribute.
See Also:
setDebuggable(boolean), BinPackage.getBoundModule_Debuggable()

setDebuggable

void setDebuggable(boolean value)
Sets the value of the 'Debuggable' attribute.

Parameters:
value - the new value of the 'Debuggable' attribute.
See Also:
isDebuggable()

getCallableBlocks

EList getCallableBlocks()
Returns the value of the 'Callable Blocks' containment reference list. The list contents are of type BinaryCallableBlock.

If the meaning of the 'Callable Blocks' containment reference list isn't clear, there really should be more of a description here...

Returns:
the value of the 'Callable Blocks' containment reference list.
See Also:
BinPackage.getBoundModule_CallableBlocks()

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.