The ClassValidator validates a value using three criteria:

1. the value adheres to the Java Language Specification rules
2. the class specified by the name is loadable
3. the class specified by the name can be instantiated

// 1.
ClassValidator validator = new ClassValidator();
// 2.
validator.setLoadable(true);
// 3.
validator.setLoadable(true);

TODO: add section about values being replaced with class instances

The DateValidator validates values against a java.text.DateFormat. There are three helper methods that create built-in validators.

1. getDateInstance returns a validator for the default date format for the default locale.
2. getTimeInstance returns a validator for the default time format for the default locale.
3. getDateTimeInstance returns a validator for the default date and time format for the default locale.

A DateValidator can also be created by passing your a custom DateFormat into the constructor.

DateFormat myFormat = DateFormat.getDateInstance( DateFormat.LONG, Locale.UK );
DateValidator myValidator = new DateValidator( myFormat );

In addition to basic format checking you can also check if the date/time specified is before/after a specific date/time. The lower bound is set using the setMinimum( java.util.Date ), and the upper bound is set using the setMaximum( java.util.Date ).

TODO: add section about values being replaced with date instances

The EnumValidator validates values against a list of allowed string values. The values that are allowed are specified in a java.util.Set and passed in to the constructor.

Set enumSet = new TreeSet();
enumSet.add("red");
enumSet.add("green");
enumSet.add("blue");
       
EnumValidator validator = new EnumValidator( enumSet );

The FileValidator validates that values represent existing files. You can also specify a combination of the following additional criteria:

1. value is a file
2. value is a directory
3. the file is writable
4. the file is readable

Each of the criteria listed here are specified using the appropriate setter.

There are three helper methods to create validators:

1. getExistingInstance returns a validator that ensures a value represents an existing file.
2. getExistingFileInstance returns a validator that ensures a value represents an existing file that is not a directory.
3. getExistingDirectoryInstance returns a validator that ensures a value represents an existing file this is a directory.

// validate that the value represents a file that exists
FileValidator validator = FileValidator.getExistingInstance();

// ensure it's a writable file
validator.setWritable( true );

The NumberValidator validates that values adhere to certain rules like the following:

1. getCurrencyInstance returns a validator for the default currency format for the default locale.
2. getPercentInstance returns a validator for the default percent format for the default locale.
3. getIntegerInstance returns a validator for the default integer format for the default locale.
4. getNumberInstance returns a validator for the default number format for the default locale.

A NumberValidator can also be created by passing your a custom NumberFormat into the constructor.

NumberFormat myFormat = NumberFormat.getCurrencyInstance( Locale.UK );
NumberValidator myValidator = new NumberValidator( myFormat );

In addition to basic format checking you can also check if the number specified is less than or greater than a specific number. The lower bound is set using the setMinimum( Number ), and the upper bound is set using the setMaximum( Number ).

A URIValidator validates that a given URI is parsable and optionally provides support for scheme validation.

URIValidator validator = new URIValidator();

A URLValidator validates that values are URLs and if you choose it will also validate the protocol is of the type you have specified.

UrlValidator validator = new UrlValidator();

// only accept https URLs
validator.setProtocol("https");