com.ibm.etools.iseries.core.search
Class ISeriesSearchFilterEventsFileParser
java.lang.Object
com.ibm.etools.iseries.core.evfparser.ISeriesEventsFileParser
com.ibm.etools.iseries.core.evfparser.ISeriesEventsFileParserLite
com.ibm.etools.iseries.core.search.ISeriesSearchEventsFileParser
com.ibm.etools.iseries.core.search.ISeriesSearchFilterEventsFileParser
- public class ISeriesSearchFilterEventsFileParser
- extends ISeriesSearchEventsFileParser
When searching filters, it is possible to have duplicate entries
This overrides the base class by changing a method which
checks to make sure there is no duplicate record in the result
view
Methods inherited from class com.ibm.etools.iseries.core.search.ISeriesSearchEventsFileParser |
getSearchResultSet, handleErrorInformationRecord, handleFeedbackCodeRecord, handleFileEndRecord, handleMapDefineRecord, handleMapEndRecord, handleMapStartRecord, handleProcessorRecord, handleProgramRecord, handleTimestampRecord, setEvfFile, setISeriesConnection, setSearchResultSet |
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
mixedConnection
protected boolean mixedConnection
ISeriesSearchFilterEventsFileParser
public ISeriesSearchFilterEventsFileParser(IFile file,
ISeriesSearchResultInputElement set,
boolean mixedConnection)
- Constructor
handleFileIDRecord
public void handleFileIDRecord(ISeriesEventsFileFileIDRecord fileIDRecord)
- This method checks for duplicate root entry
- Overrides:
handleFileIDRecord
in class ISeriesSearchEventsFileParser
- See Also:
ISeriesEventsFileParser.handleFileIDRecord(ISeriesEventsFileFileIDRecord)
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.