Remote Systems
v6.4.1

com.ibm.etools.systems.core.ui.validators
Class ValidatorServerPortInput

java.lang.Object
  extended bycom.ibm.etools.systems.core.ui.validators.ValidatorIntegerInput
      extended bycom.ibm.etools.systems.core.ui.validators.ValidatorPortInput
          extended bycom.ibm.etools.systems.core.ui.validators.ValidatorServerPortInput
All Implemented Interfaces:
ISystemValidator

public class ValidatorServerPortInput
extends ValidatorPortInput


Field Summary
 
Fields inherited from class com.ibm.etools.systems.core.ui.validators.ValidatorPortInput
copyright, MAXIMUM_PORT_NUMBER
 
Fields inherited from class com.ibm.etools.systems.core.ui.validators.ValidatorIntegerInput
allowBlank, currentMessage, emptyMsg, invalidMsg, number
 
Fields inherited from interface com.ibm.etools.systems.core.ui.validators.ISystemValidator
Copyright
 
Constructor Summary
ValidatorServerPortInput()
           
 
Method Summary
 String isValid(Object input)
           
 String isValid(String input)
           
 
Methods inherited from class com.ibm.etools.systems.core.ui.validators.ValidatorIntegerInput
getMaximumNameLength, getNumber, getSystemMessage, setBlankAllowed, setErrorMessages, validate
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Constructor Detail

ValidatorServerPortInput

public ValidatorServerPortInput()
Method Detail

isValid

public String isValid(Object input)
Overrides:
isValid in class ValidatorPortInput
See Also:
ICellEditorValidator

isValid

public String isValid(String input)
Overrides:
isValid in class ValidatorPortInput
See Also:
ValidatorIntegerInput.isValid(java.lang.String)

Remote Systems
v6.4.1

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.