com.ibm.etools.systems.references.impl
Class SystemPersistableReferencedObjectHelper
java.lang.Object
com.ibm.etools.systems.references.impl.SystemReferencedObjectHelper
com.ibm.etools.systems.references.impl.SystemPersistableReferencedObjectHelper
- All Implemented Interfaces:
- ISystemPersistableReferencedObject, ISystemReferencedObject
- public class SystemPersistableReferencedObjectHelper
- extends SystemReferencedObjectHelper
- implements ISystemPersistableReferencedObject
This class extends the support for a class that supports being managing by a transient
in-memory reference to one which also supports the persistance of such references.
To do this, such a referencable class must be able to return a name that is
so unique that it can be used after restoration from disk to resolve a pointer to this
specific object, in memory.
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
copyright
public static final String copyright
- See Also:
- Constant Field Values
SystemPersistableReferencedObjectHelper
protected SystemPersistableReferencedObjectHelper(String referenceName)
- Constructor for SystemPersistableReferencedObjectHelper
- Parameters:
referenceName
- The unique name that can be stored to identify this object.
getReferenceName
public String getReferenceName()
- Return the unique reference name of this object, as set in the constructor
- Specified by:
getReferenceName
in interface ISystemPersistableReferencedObject
setReferenceName
public void setReferenceName(String name)
- Set the unique reference name of this object. Overrides what was set in
the constructor. Typically called on rename operation.
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.