Rational Developer for Power Systems Software
V7.6

com.ibm.etools.systems.editor.actions
Class ValidatorDate

java.lang.Object
  extended by com.ibm.etools.systems.editor.actions.ValidatorDate

public class ValidatorDate
extends Object

This class is used to validate the dates on the Filter by Date dialog.

Since:
6.0.1 55059

Field Summary
static String Copyright
           
static String DATE_FORMAT
           
 
Constructor Summary
ValidatorDate()
           
 
Method Summary
 int getMaximumNameLength()
           
 SystemMessage getSystemMessage()
           
 String isValid(Object value)
           
 String isValid(String newText)
           
 void setCheckMagicYear(String text)
          Sets the from date and indicates that Magic year checking should be performed.
 SystemMessage validate(String text)
           
 
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

DATE_FORMAT

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

ValidatorDate

public ValidatorDate()
Method Detail

getMaximumNameLength

public int getMaximumNameLength()

getSystemMessage

public SystemMessage getSystemMessage()

validate

public SystemMessage validate(String text)

isValid

public String isValid(String newText)

isValid

public String isValid(Object value)

setCheckMagicYear

public void setCheckMagicYear(String text)
Sets the from date and indicates that Magic year checking should be performed.

Parameters:
-

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.