com.ibm.etools.iseries.rse.ui.search
Class SearchFilterEventsFileParser
java.lang.Object
com.ibm.etools.iseries.rse.util.evfparser.QSYSEventsFileParser
com.ibm.etools.iseries.rse.util.evfparser.QSYSEventsFileParserLite
com.ibm.etools.iseries.rse.ui.search.SearchEventsFileParser
com.ibm.etools.iseries.rse.ui.search.SearchFilterEventsFileParser
public class SearchFilterEventsFileParser
- extends SearchEventsFileParser
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.rse.ui.search.SearchEventsFileParser |
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
SearchFilterEventsFileParser
public SearchFilterEventsFileParser(IFile file,
SearchResultInputElement set,
boolean mixedConnection)
- Constructor
handleFileIDRecord
public void handleFileIDRecord(QSYSEventsFileFileIDRecord fileIDRecord)
- This method checks for duplicate root entry
- Overrides:
handleFileIDRecord
in class SearchEventsFileParser
- See Also:
com.ibm.etools.iseries.core.evfparser.ISeriesEventsFileParser#handleFileIDRecord(ISeriesEventsFileFileIDRecord)
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.