Overview  Package   Class  Tree  Serialized  Deprecated  Index  Help 
Rational Developer for Power Systems Software
V7.6
 PREV CLASS   NEXT CLASS FRAMES    NO FRAMES    
SUMMARY: NESTED | FIELD | CONSTR | METHOD DETAIL: FIELD | CONSTR | METHOD

com.ibm.etools.iseries.rse.ui.validators
Class ValidatorQSYSLibraryListFilter

java.lang.Object
  extended by com.ibm.etools.iseries.rse.ui.validators.ValidatorQSYSLibraryListFilter

public class ValidatorQSYSLibraryListFilter
extends Object

This class is used in the New Library List Filter wizard, when a filter pool is selected by the user. It validates that there is not already a library list filter for that filter pool.

Field Summary
static String Copyright
           
 
Constructor Summary
ValidatorQSYSLibraryListFilter()
          Constructor
 
Method Summary
 SystemMessage validate(ISystemFilterPool filterPool)
          Called to do verification given the selected filter pool
 
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
Constructor Detail

ValidatorQSYSLibraryListFilter

public ValidatorQSYSLibraryListFilter()
Constructor

Method Detail

validate

public SystemMessage validate(ISystemFilterPool filterPool)
Called to do verification given the selected filter pool

Parameters:
filterPool - the target filter pool selected by the user.
Returns:
A error message string if the verify failed, or null if it is successful.
Overview  Package   Class  Tree  Serialized  Deprecated  Index  Help 
Rational Developer for Power Systems Software
V7.6
 PREV CLASS   NEXT CLASS FRAMES    NO FRAMES    
SUMMARY: NESTED | FIELD | CONSTR | METHOD DETAIL: FIELD | CONSTR | METHOD
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.