All Classes and Interfaces

Class
Description
Base class for ValidationListeners.
Convenience base class for validators.
 
Converts validators.
 
Encapsulates validation of the combination of several UI components within a ValidationGroup.
An enumeration of validator factories for commonly needed forms of selection validaton.
A separate exception class for invalid user (or stored values).
Wrapper to allow reflective access to NetBeans' NbBundle API.
Represents a problem produced by a validator.
A collection of problems, to which a Validator can add additional problems.
 
 
enum indicating Severity, used for classifying Problem instances.
 
 
An enumeration of validator factories for commonly needed forms of validation such as non-empty strings, valid file names and URLs and so forth.
Factory class for creating ValidationUI instances that can decorate a Swing GUI-component when it has a Problem.
ValidationGroup subclass specialized for handling Swing components.
Interface for things that are able to validate themselves, such as email addresses.
A ValidationGroup logically groups a set of GUI-components, such as text fields, lists, tables, comboboxes etc, each validated by one or more validators (such as the built-in ones provided by the framework in StringValidators).
Optional interface which can be implemented on a component to indicate that it supplies validation.
Common superclass for ValidationGroup and ValidationListener, providing a common API for forcing revalidation of the managed UI component or components, see ValidationItem.performValidation(), and for temporarily suspending validation, see ValidationItem.runWithValidationSuspended(java.lang.Runnable)
Abstract base class for UI component listeners that can trigger validation when an interesting event occurs, and when requested perform validation of the UI component using a Validator.
Factory for listeners on a particular type of component with a particular type of model.
A simple panel which can display a problem, fire changes when the problem changes.
Determines what event on the component will trigger running validation.
User interface controller which can show the user one problem.
Validator that can validate some aspect of a component's model, and indicate problems to the user.
 
Some utilities for manipulating and creating new Validators, useful in many situations.