Remote Systems
v6.4.1

com.ibm.etools.systems.subsystems.impl
Class AbstractResource

java.lang.Object
  extended bycom.ibm.etools.systems.subsystems.impl.AbstractResource
All Implemented Interfaces:
IAdaptable

public abstract class AbstractResource
extends Object
implements IAdaptable

This class can be used as the base class for model objects that represent remote resources returned from the subsystem via resolveFilterStrings. Its advantages are:


Field Summary
static String Copyright
           
 
Constructor Summary
AbstractResource()
          Constructor.
AbstractResource(SubSystem parentSubSystem)
          Default constructor
 
Method Summary
 Object getAdapter(Class adapter)
           
 SubSystem getSubSystem()
          Returns the parent SubSystem which produced this remote resource.
 void setSubSystem(SubSystem parentSubSystem)
          Resets the parent SubSystem.
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

Copyright

public static final String Copyright
See Also:
Constant Field Values
Constructor Detail

AbstractResource

public AbstractResource(SubSystem parentSubSystem)
Default constructor


AbstractResource

public AbstractResource()
Constructor.

See Also:
setSubSystem(SubSystem)
Method Detail

getAdapter

public Object getAdapter(Class adapter)
Specified by:
getAdapter in interface IAdaptable
See Also:
IAdaptable.getAdapter(Class)

getSubSystem

public SubSystem getSubSystem()
Returns the parent SubSystem which produced this remote resource.

Returns:
SubSystem

setSubSystem

public void setSubSystem(SubSystem parentSubSystem)
Resets the parent SubSystem.

Parameters:
parentSubSystem - The parentSubSystem to set

Remote Systems
v6.4.1

Copyright © 2005 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.