Remote Systems
v6.4.1

com.ibm.etools.systems.universalfilesubsys.impl
Class UniversalFileImpl.StatusListener

java.lang.Object
  extended bycom.ibm.etools.systems.universalfilesubsys.impl.UniversalFileImpl.StatusListener
All Implemented Interfaces:
IDomainListener
Direct Known Subclasses:
UniversalFileImpl.AttributesListener, UniversalFileImpl.CanWriteListener
Enclosing class:
UniversalFileImpl

public abstract class UniversalFileImpl.StatusListener
extends Object
implements IDomainListener


Field Summary
protected  Object _child
           
 
Fields inherited from interface com.ibm.etools.systems.dstore.extra.internal.extra.IDomainListener
Copyright
 
Constructor Summary
UniversalFileImpl.StatusListener(DataElement status, DataElement element, Object child)
           
 
Method Summary
 void domainChanged(DomainEvent e)
           
 Shell getShell()
           
protected abstract  boolean handleResponse(DataElement obj)
           
 boolean listeningTo(DomainEvent e)
           
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

_child

protected Object _child
Constructor Detail

UniversalFileImpl.StatusListener

public UniversalFileImpl.StatusListener(DataElement status,
                                        DataElement element,
                                        Object child)
Method Detail

getShell

public Shell getShell()
Specified by:
getShell in interface IDomainListener

listeningTo

public boolean listeningTo(DomainEvent e)
Specified by:
listeningTo in interface IDomainListener

domainChanged

public void domainChanged(DomainEvent e)
Specified by:
domainChanged in interface IDomainListener

handleResponse

protected abstract boolean handleResponse(DataElement obj)

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.