Remote Systems
v6.4.1

com.ibm.etools.systems.filters
Interface SystemFilterPoolReference

All Superinterfaces:
ISystemPersistableReferencingObject, ISystemReferencingObject, SystemFilterContainerReference, SystemPersistableReferencingObject, SystemReferencingObject
All Known Implementing Classes:
SystemFilterPoolReferenceImpl

public interface SystemFilterPoolReference
extends SystemPersistableReferencingObject, SystemFilterContainerReference


Field Summary
static String copyright
           
 
Method Summary
 SystemFilterPoolReferenceManager getFilterPoolReferenceManager()
          Return the reference manager which is managing this filter reference framework object.
 String getFullName()
          Return fully qualified name that includes the filter pool managers name
 SystemFilterPoolReferenceManagerProvider getProvider()
          Return the object which instantiated the pool reference manager object.
 SystemFilterPool getReferencedFilterPool()
          Return referenced filter pool object
 String getReferencedFilterPoolManagerName()
          Return name of the filter pool manager containing the pool we reference.
 String getReferencedFilterPoolName()
          Return name of the filter pool we reference The pool name is stored qualified by the manager name, so we first have to strip it off.
 void resetReferencedFilterPoolName(String newName)
          Reset the name of the filter pool we reference.
 void setReferenceToFilterPool(SystemFilterPool pool)
          Set the filter pool that we reference.
 
Methods inherited from interface com.ibm.etools.systems.references.SystemPersistableReferencingObject
getParentReferenceManager, getReferencedObjectName, setParentReferenceManager, setReferencedObjectName
 
Methods inherited from interface com.ibm.etools.systems.references.ISystemReferencingObject
getReferencedObject, isReferenceBroken, removeReference, setReferenceBroken, setReferencedObject
 
Methods inherited from interface com.ibm.etools.systems.references.ISystemPersistableReferencingObject
setReferencedObject
 
Methods inherited from interface com.ibm.etools.systems.filters.SystemFilterContainerReference
getExistingSystemFilterReference, getFilterCount, getName, getReferencedSystemFilterContainer, getSystemFilterReference, getSystemFilterReferences, hasFilters
 

Field Detail

copyright

public static final String copyright
See Also:
Constant Field Values
Method Detail

getFilterPoolReferenceManager

public SystemFilterPoolReferenceManager getFilterPoolReferenceManager()
Return the reference manager which is managing this filter reference framework object.


getProvider

public SystemFilterPoolReferenceManagerProvider getProvider()
Return the object which instantiated the pool reference manager object. Makes it easy to get back to the point of origin, given any filter reference framework object


getReferencedFilterPoolName

public String getReferencedFilterPoolName()
Return name of the filter pool we reference The pool name is stored qualified by the manager name, so we first have to strip it off.


getReferencedFilterPoolManagerName

public String getReferencedFilterPoolManagerName()
Return name of the filter pool manager containing the pool we reference. The pool name is stored qualified by the manager name, so we get it from there.


resetReferencedFilterPoolName

public void resetReferencedFilterPoolName(String newName)
Reset the name of the filter pool we reference. Called on filter pool rename operations


setReferenceToFilterPool

public void setReferenceToFilterPool(SystemFilterPool pool)
Set the filter pool that we reference. This also calls addReference(this) on that pool!


getReferencedFilterPool

public SystemFilterPool getReferencedFilterPool()
Return referenced filter pool object


getFullName

public String getFullName()
Return fully qualified name that includes the filter pool managers name


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.