com.ibm.etools.systems.core
Class SystemRemoteDirectoryMatcher
java.lang.Object
com.ibm.etools.systems.core.SystemRemoteObjectMatcher
com.ibm.etools.systems.core.SystemRemoteDirectoryMatcher
- public class SystemRemoteDirectoryMatcher
- extends SystemRemoteObjectMatcher
This class encapsulates all the criteria required to identify a match on a remote
* system directory object.
*
* Use the static method getDirectoryMatcher()
* to get an default instance that matches on any directory of any name.
*
* You only need to instantiate this class if you want to match on a directory of a
* particular name.
* @see com.ibm.etools.systems.core.ui.view.ISystemRemoteElementAdapter
Methods inherited from class com.ibm.etools.systems.core.SystemRemoteObjectMatcher |
appliesTo, endsWithAsterisk, getCategoryFilter, getNameFilter, getSubSubTypeFilter, getSubSystemFactoryCategoryFilter, getSubSystemFactoryId, getSubTypeFilter, getSystemTypesFilter, getTypeFilter, resolveSymbols, startsWithAsterisk, stripLeadingAsterisk, stripTrailingAsterisk |
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
inst
public static SystemRemoteDirectoryMatcher inst
category
public static final String category
- See Also:
- Constant Field Values
type
public static final String type
- See Also:
- Constant Field Values
SystemRemoteDirectoryMatcher
public SystemRemoteDirectoryMatcher(String nameFilter)
- Constructor.
* You only need to instantiate yourself if you want to match on a directory
* of a particular name.
* Otherwise, call
getDirectoryMatcher()
.
getDirectoryMatcher
public static SystemRemoteDirectoryMatcher getDirectoryMatcher()
- Return an instance that will match on any directory of any name from any remote system
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.