Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.edit.wizards.validator
Class ValidatorProcedureParameterName

java.lang.Object
  extended by ValidatorSpecialChar
      extended by com.ibm.etools.iseries.edit.wizards.validator.ValidatorFieldType
          extended by com.ibm.etools.iseries.edit.wizards.validator.ValidatorProcedureParameterName

public class ValidatorProcedureParameterName
extends ValidatorFieldType


Field Summary
 
Fields inherited from class com.ibm.etools.iseries.edit.wizards.validator.ValidatorFieldType
Copyright, FIELDTYPE_INVALID_CHARS, FIELDTYPE_MAXLENGTH_NAME, reservedPage, reservedWordsForDate
 
Constructor Summary
ValidatorProcedureParameterName(boolean emptyAllowed, String specialChars)
          Constructor override the errormessages of superclass
ValidatorProcedureParameterName(String specialChars)
           
 
Method Summary
 
Methods inherited from class com.ibm.etools.iseries.edit.wizards.validator.ValidatorFieldType
doMessageSubstitution, followNamingRule, getMaximumNameLength, isEmptyAllowed, isReserved, isReservedForDate, isReservedForPage, isSyntaxOk, isValid, isValidChar, setEmptyAllowed, setFunctionAllowed, setReservedAllowed
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Constructor Detail

ValidatorProcedureParameterName

public ValidatorProcedureParameterName(String specialChars)

ValidatorProcedureParameterName

public ValidatorProcedureParameterName(boolean emptyAllowed,
                                       String specialChars)
Constructor override the errormessages of superclass


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.