Rational Developer for Power Systems Software
V7.6

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

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

public class ValidatorCompileCommandLabel
extends ValidatorUniqueString

This is a copy of the open RSE ValidatorCompileCommandLabel, but with some modifications, due to NLS problems in open RSE. TODO: Remove when we move to open RSE 3.1 when it can fix the nls bugs


Field Summary
static String copyright
           
protected  boolean fUnique
           
static int MAX_CMDLABEL_LENGTH
           
protected  SystemMessage msg_Invalid
           
protected  IWorkspace workspace
           
 
Constructor Summary
ValidatorCompileCommandLabel()
          Use this constructor when the name need not be unique, and you just want the syntax checking.
ValidatorCompileCommandLabel(Collection existingLabelList)
          Use this constructor when you have a list of existing labels.
ValidatorCompileCommandLabel(String[] existingLabelList)
          Use this constructor when you have an array of existing labels.
 
Method Summary
protected  boolean checkForBadCharacters(String newText)
          Overridable method for invalidate character check, beyond what this class offers
 SystemMessage getInvalidMessage(String substitutionString)
           
 int getMaximumNameLength()
          Return the max length for compile commands: 50
 SystemMessage getNotUniqueMessage(String substitutionString)
           
 SystemMessage isSyntaxOk(String newText)
          Validate each character.
 String isValid(String newText)
          Copied from ValidatorUniqueString, which slight modifications for the NLS problems in open RSE 3.0
 String toString()
           
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
 

Field Detail

copyright

public static String copyright

MAX_CMDLABEL_LENGTH

public static final int MAX_CMDLABEL_LENGTH
See Also:
Constant Field Values

fUnique

protected boolean fUnique

msg_Invalid

protected SystemMessage msg_Invalid

workspace

protected IWorkspace workspace
Constructor Detail

ValidatorCompileCommandLabel

public ValidatorCompileCommandLabel(Collection existingLabelList)
Use this constructor when you have a list of existing labels. The collection will not be modified by the validator.


ValidatorCompileCommandLabel

public ValidatorCompileCommandLabel(String[] existingLabelList)
Use this constructor when you have an array of existing labels.


ValidatorCompileCommandLabel

public ValidatorCompileCommandLabel()
Use this constructor when the name need not be unique, and you just want the syntax checking. Or if you will call setExistingNamesList later.

Method Detail

checkForBadCharacters

protected boolean checkForBadCharacters(String newText)
Overridable method for invalidate character check, beyond what this class offers

Returns:
true if valid, false if not

toString

public String toString()

isSyntaxOk

public SystemMessage isSyntaxOk(String newText)
Validate each character. Override of parent method. Override yourself to refine the error checking.


getMaximumNameLength

public int getMaximumNameLength()
Return the max length for compile commands: 50


isValid

public String isValid(String newText)
Copied from ValidatorUniqueString, which slight modifications for the NLS problems in open RSE 3.0


getInvalidMessage

public SystemMessage getInvalidMessage(String substitutionString)

getNotUniqueMessage

public SystemMessage getNotUniqueMessage(String substitutionString)

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.