com.ibm.etools.iseries.rse.ui.view.objtable.viewInput
Class OTVInputSystemFilterStringReference
java.lang.Object
com.ibm.etools.iseries.rse.ui.view.objtable.viewInput.OTVInput
com.ibm.etools.iseries.rse.ui.view.objtable.viewInput.OTVInputSystemFilterReference
com.ibm.etools.iseries.rse.ui.view.objtable.viewInput.OTVInputSystemFilterStringReference
- All Implemented Interfaces:
- IObjectTableViewInput
public class OTVInputSystemFilterStringReference
- extends OTVInputSystemFilterReference
Extends from class OTVInputSystemFilterReference so that
we can share the getElements method. We will just be
the case here of only always a single filter string to it.
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
getTitle
public String getTitle()
- Specified by:
getTitle
in interface IObjectTableViewInput
- Overrides:
getTitle
in class OTVInputSystemFilterReference
getHistoryEntryName
public String getHistoryEntryName()
- Specified by:
getHistoryEntryName
in interface IObjectTableViewInput
- Overrides:
getHistoryEntryName
in class OTVInputSystemFilterReference
getSystemFilter
public ISystemFilter getSystemFilter()
- For SystemFilterString's; Want to get the SystemFilter that contains them.
- Specified by:
getSystemFilter
in interface IObjectTableViewInput
- Overrides:
getSystemFilter
in class OTVInputSystemFilterReference
getParentFilterReference
public ISystemFilterReference getParentFilterReference()
getInput
public Object getInput()
- Description copied from class:
OTVInputSystemFilterReference
- getInput: Used so the subclass can substitute it's input value in the
other common method (getElements).
- Overrides:
getInput
in class OTVInputSystemFilterReference
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.