Remote Systems
v6.4.1

com.ibm.etools.systems.subsystems
Class RemoteFileIOException

java.lang.Object
  extended byjava.lang.Throwable
      extended byjava.lang.Exception
          extended bycom.ibm.etools.systems.core.messages.SystemMessageException
              extended bycom.ibm.etools.systems.subsystems.RemoteFileException
                  extended bycom.ibm.etools.systems.subsystems.RemoteFileIOException
All Implemented Interfaces:
Serializable
Direct Known Subclasses:
RemoteFileCancelledException

public class RemoteFileIOException
extends RemoteFileException

Exception thrown when attempting an operation and it fails for IO reasons, such as the file is read-only.

The original remote system's io message is always embedded and retrievable via getRemoteException().

See Also:
Serialized Form

Field Summary
static String copyright
           
 
Fields inherited from class com.ibm.etools.systems.core.messages.SystemMessageException
Copyright
 
Constructor Summary
RemoteFileIOException(Exception remoteException)
          Constructor
 
Methods inherited from class com.ibm.etools.systems.subsystems.RemoteFileException
getRemoteException
 
Methods inherited from class com.ibm.etools.systems.core.messages.SystemMessageException
getSystemMessage, hasLongID, setSystemMessage
 
Methods inherited from class java.lang.Throwable
fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
 

Field Detail

copyright

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

RemoteFileIOException

public RemoteFileIOException(Exception remoteException)
Constructor


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.