com.ibm.etools.systems.universal.util
Class ConnectionStatusListener
java.lang.Object
com.ibm.etools.systems.universal.util.ConnectionStatusListener
- All Implemented Interfaces:
- IDomainListener
- public class ConnectionStatusListener
- extends Object
- implements IDomainListener
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
_dataStoreStatus
protected DataElement _dataStoreStatus
_connection
protected ISystem _connection
_connectionDown
protected boolean _connectionDown
ConnectionStatusListener
public ConnectionStatusListener(DataElement status,
ISystem connection)
- Parameters:
status
- The status element for the DataStore handling this connection.
internalGetShell
protected Shell internalGetShell()
handleConnectionDown
protected void handleConnectionDown()
- The handleConnectionDown method is invoked if the network connection between the
client and server goes down while connected. Currently this method displays
an error to the user and the subsytem is disconnected.
listeningTo
public boolean listeningTo(DomainEvent event)
- Specified by:
listeningTo
in interface IDomainListener
- See Also:
IDomainListener.listeningTo(DomainEvent)
domainChanged
public void domainChanged(DomainEvent event)
- Specified by:
domainChanged
in interface IDomainListener
- See Also:
IDomainListener.domainChanged(DomainEvent)
getShell
public Shell getShell()
- Specified by:
getShell
in interface IDomainListener
- See Also:
IDomainListener.getShell()
isConnectionDown
public boolean isConnectionDown()
- Callback method for the ISystem to determine if the connection is down. This is
called by the disconnect method to determine if we can do saves or not.
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.