com.ibm.etools.systems.universalfilesubsys.impl
Class UniversalSearchResultConfigurationImpl
java.lang.Object
com.ibm.etools.systems.subsystems.impl.RemoteSearchResultConfigurationImpl
com.ibm.etools.systems.universalfilesubsys.impl.UniversalSearchResultConfigurationImpl
- All Implemented Interfaces:
- IRemoteSearchConstants, IRemoteSearchResultConfiguration
- public class UniversalSearchResultConfigurationImpl
- extends RemoteSearchResultConfigurationImpl
Methods inherited from class com.ibm.etools.systems.subsystems.impl.RemoteSearchResultConfigurationImpl |
addResult, dispose, getParentResultSet, getResults, getResultsSize, getSearchString, getSearchTarget, getStatus, removeAndAddResult, removeResult, removeResults, setParentResultSet, setSearchString, setSearchTarget, setStatus |
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
statusObject
protected DataElement statusObject
UniversalSearchResultConfigurationImpl
public UniversalSearchResultConfigurationImpl(IRemoteSearchResultSet resultSet,
Object searchObject,
SystemSearchString string)
- Constructor to create a universal search result configuration.
- Parameters:
resultSet
- the parent result set.searchObject
- the search target.string
- the search string.
setStatusObject
public void setStatusObject(DataElement statusObject)
getStatusObject
public DataElement getStatusObject()
cancel
public void cancel()
- Description copied from class:
RemoteSearchResultConfigurationImpl
- Does nothing.
- Specified by:
cancel
in interface IRemoteSearchResultConfiguration
- Overrides:
cancel
in class RemoteSearchResultConfigurationImpl
- See Also:
IRemoteSearchResultConfiguration.cancel()
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.