com.ibm.etools.systems.universal.util
Class FileTransferStatusListener
java.lang.Object
com.ibm.etools.systems.universal.util.StatusChangeListener
com.ibm.etools.systems.universal.util.FileTransferStatusListener
- All Implemented Interfaces:
- ICommunicationsListener, IDomainListener
- public class FileTransferStatusListener
- extends StatusChangeListener
Methods inherited from class com.ibm.etools.systems.universal.util.StatusChangeListener |
communicationsStateChange, domainChanged, getShell, getStatus, isNetworkDown, isPassiveCommunicationsListener, listeningTo, setDone, setStatus, waitForUpdate, waitForUpdate, waitForUpdate, wasCancelled, whatIsGoingOn |
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
_remotePath
protected String _remotePath
_log
protected DataElement _log
_statusElement
protected DataElement _statusElement
FileTransferStatusListener
public FileTransferStatusListener(String remotePath,
Shell shell,
IProgressMonitor monitor,
ISystem system,
DataStore ds,
DataElement uploadLog)
throws Exception
findOrCreateUploadStatus
protected DataElement findOrCreateUploadStatus(DataStore ds)
determineStatusDone
protected boolean determineStatusDone()
- Description copied from class:
StatusChangeListener
- Determines whether the status is done.
- Overrides:
determineStatusDone
in class StatusChangeListener
- Returns:
true
if status done, false
otherwise.- See Also:
StatusChangeListener.determineStatusDone()
uploadHasFailed
public boolean uploadHasFailed()
getErrorMessage
public String getErrorMessage()
getRemotePath
public String getRemotePath()
setRemotePath
public void setRemotePath(String remotePath)
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.