Using the Standard Validators
JavaServer Faces technology provides a set of standard classes and associated tags that page authors and application developers can use to validate a component's data. Table 10-7 lists all the standard validator classes and the tags that allow you to use the validators from the page.
All these validator classes implement the
Validatorinterface. Component writers and application developers can also implement this interface to define their own set of constraints for a component's value.When you want to register a standard validator on a component, you just nest the standard validator's tag inside the tag representing a component that implements
EditableValueHolderand provide the necessary constraints, if the validator tag requires it. Validation can be performed only on components that implementEditableValueHolderbecause these components accept values that can be validated.Each standard validator supports a binding attribute, which is used to bind a validator implementation to a backing bean property, similarly to the way binding attributes are used with converter and listener tags, as described previously in this chapter.
Similarly to the standard converters, each of these validators has a one or more standard error messages associated with it. If you have registered one of these validators onto a component on your page, and the validator is not able to validate the component's value, the validator's error message will display on the page. For example, the error message that displays when the component's value exceeds the maximum value allowed by LongRangeValidator is the following:
In this case the {1} substitution parameter is replaced by the component's label or ID, and the {0} substitution parameter is replaced with the maximum value allowed by the validator. See section 2.5.4 of the JavaServer Faces specification for the complete list of error messages.
This section shows you how to use the
LongRangeValidatorimplementation. The other validators work in a similar way.See The UIMessage and UIMessages Components for information on how to display validation error messages on the page when validation fails.
Requiring a Value
The
nameinputTexttag on thebookcashier.jsppage has arequiredattribute, which is set totrue. Because of this, the JavaServer Faces implementation checks whether the value of the component is null or is an empty String.If your component must have a non-
nullvalue or aStringvalue at least one character in length, you should add arequiredattribute to your component tag and set it totrue. If your tag does have arequiredattribute that is set totrueand the value isnullor a zero-length string, no other validators registered on the tag are called. If your tag does not have arequiredattribute set totrue, other validators registered on the tag are called, but those validators must handle the possibility of anullor zero-length string.Here is the
nameinputTexttag:Using the LongRangeValidator
The Duke's Bookstore application uses a
validateLongRangetag on thequantityinput field of thebookshowcart.jsppage:<h:inputText id="quantity" size="4" value="#{item.quantity}"> <f:validateLongRange minimum="1"/> </h:inputText> <h:message for="quantity"/>This tag requires that the user enter a number that is at least 1. The
sizeattribute specifies that the number can have no more than four digits. ThevalidateLongRangetag also has amaximumattribute, with which you can set a maximum value of the input.The attributes of all the standard validator tags accept value expressions. This means that the attributes can reference backing bean properties rather than specify literal values. For example, the
validateLongRangetag in the preceding example can reference a backing bean property calledminimumto get the minimum value acceptable to the validator implementation: