Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.rse.ui
Class QSYSRemoteRecordMatcher

java.lang.Object
  extended by SystemRemoteObjectMatcher
      extended by com.ibm.etools.iseries.rse.ui.QSYSRemoteRecordMatcher

public class QSYSRemoteRecordMatcher
extends SystemRemoteObjectMatcher

This class encapsulates all the criteria required to identify a match on a record in a remote iSeries system QSYS file object.

Use the static method getRecordTypeMatcher() to get an default instance that matches on any record of any name of any type.

You only need to instantiate this class if you want to match on a record of a particular name.

See Also:
com.ibm.etools.systems.core.ui.view.ISystemRemoteElement

Field Summary
static String category
           
static String copyright
           
static QSYSRemoteRecordMatcher inst
           
 
Constructor Summary
QSYSRemoteRecordMatcher(String nameFilter)
          Constructor.
 
Method Summary
static QSYSRemoteRecordMatcher getRecordTypeMatcher()
          Return an instance that will match on any record of any name.
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

copyright

public static final String copyright
See Also:
Constant Field Values

inst

public static QSYSRemoteRecordMatcher inst

category

public static final String category
See Also:
Constant Field Values
Constructor Detail

QSYSRemoteRecordMatcher

public QSYSRemoteRecordMatcher(String nameFilter)
Constructor. You only need to instantiate yourself if you want to match on a record of a particular name.

Otherwise, call #getFieldTypeMatcher().

Method Detail

getRecordTypeMatcher

public static QSYSRemoteRecordMatcher getRecordTypeMatcher()
Return an instance that will match on any record of any name.


Rational Developer for Power Systems Software
V7.6

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.