Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.rse.ui.resources
Class QSYSSrcPhysicalFileMemberTransientReader

java.lang.Object
  extended by com.ibm.etools.iseries.rse.ui.resources.QSYSSrcPhysicalFileMemberTransientReader
All Implemented Interfaces:
ISequentialFileReader

public class QSYSSrcPhysicalFileMemberTransientReader
extends Object
implements ISequentialFileReader

Transient and Bidi visual reader for webfacing conversion. This reader is transient in that it downloads the member to a temporary


Field Summary
static String copyright
           
 
Constructor Summary
QSYSSrcPhysicalFileMemberTransientReader(IQSYSMember member, boolean bidiVisual)
           
 
Method Summary
 String readNextLine()
          Return the next line.
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

copyright

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

QSYSSrcPhysicalFileMemberTransientReader

public QSYSSrcPhysicalFileMemberTransientReader(IQSYSMember member,
                                                boolean bidiVisual)
                                         throws Exception
Parameters:
member -
transientReader - true if you want the file deleted after its been read, false otherwise.
Throws:
Exception
Method Detail

readNextLine

public String readNextLine()
                    throws IOException
Return the next line.

Specified by:
readNextLine in interface ISequentialFileReader
Returns:
the next line or null if the last line has been returned.
Throws:
IOException - if there is any problem reading
See Also:
ReaderLineScanner

Rational Developer for Power Systems Software
V7.6

Copyright © 2011 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.