com.ibm.etools.iseries.rse.util.evfparser
Class EventsFileParser
java.lang.Object
WorkspaceModifyOperation
com.ibm.etools.iseries.rse.util.evfparser.EventsFileParser
public class EventsFileParser
- extends WorkspaceModifyOperation
This is an operation that parses an event file, and opens it in the Error List view
|
Constructor Summary |
EventsFileParser(IFile newFile,
IFile oldFile,
IHost host,
String srcType)
|
EventsFileParser(IFile newFile,
IFile oldFile,
IHost host,
String srcType,
String projectName)
|
EventsFileParser(IFile newFile,
IFile oldFile,
IHost host,
String srcType,
String projectName,
boolean useDefaultEncoding)
|
|
Method Summary |
void |
execute(IProgressMonitor monitor)
|
SystemMessage |
getException()
Used to retrieve any errors found when parsing. |
| 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
EventsFileParser
public EventsFileParser(IFile newFile,
IFile oldFile,
IHost host,
String srcType)
EventsFileParser
public EventsFileParser(IFile newFile,
IFile oldFile,
IHost host,
String srcType,
String projectName)
EventsFileParser
public EventsFileParser(IFile newFile,
IFile oldFile,
IHost host,
String srcType,
String projectName,
boolean useDefaultEncoding)
execute
public void execute(IProgressMonitor monitor)
getException
public SystemMessage getException()
- Used to retrieve any errors found when parsing. EVFC6009E is retrieved. Caller must provide substitution variables:
%1 Events file name
%2 location
- Returns:
- null if there was no exception, otherwise a SystemMessage
- Since:
- 6.0
Copyright 2009 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.