com.ibm.etools.systems.files.importexport.files
Class RemoteFileImportDescriptionReader
java.lang.Object
com.ibm.etools.systems.files.importexport.files.RemoteFileImportDescriptionReader
- All Implemented Interfaces:
- IRemoteFileImportDescriptionReader
- public class RemoteFileImportDescriptionReader
- extends Object
- implements IRemoteFileImportDescriptionReader
Remote file import description reader.
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
fInputStream
protected InputStream fInputStream
subsystem
protected RemoteFileSubSystem subsystem
RemoteFileImportDescriptionReader
public RemoteFileImportDescriptionReader(InputStream inputStream)
- Constructor.
read
public void read(RemoteFileImportData importData)
throws CoreException
- Specified by:
read
in interface IRemoteFileImportDescriptionReader
- Throws:
CoreException
- See Also:
IRemoteFileImportDescriptionReader.read(com.ibm.etools.systems.files.importexport.files.RemoteFileImportData)
readXML
public RemoteFileImportData readXML(RemoteFileImportData importData)
throws IOException,
SAXException
- Throws:
IOException
SAXException
getBooleanAttribute
protected boolean getBooleanAttribute(Element element,
String name)
throws IOException
- Throws:
IOException
close
public void close()
throws CoreException
- Specified by:
close
in interface IRemoteFileImportDescriptionReader
- Throws:
CoreException
- See Also:
IRemoteFileImportDescriptionReader.close()
getStatus
public IStatus getStatus()
- Specified by:
getStatus
in interface IRemoteFileImportDescriptionReader
- See Also:
IRemoteFileImportDescriptionReader.getStatus()
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.