Page History

...

In short, instead of specifying the types found in collections and maps as documented in Type Conversion, the collection's generic type is used. This means you most likely don't need any ClassName-conversion.properties files.

Validation Annotations

If you want to use annotatin based validation, you have to annotate the class or interface with Validation Annotation.

These are the standard validator annotations that come with XWork-tiger:

• #ConversionErrorFieldValidator
• #DateRangeFieldValidator
• #EmailValidator
• #ExpressionValidator
• #FieldExpressionValidator
• #IntRangeFieldValidator
• #RegexFieldValidator
• #RequiredFieldValidator
• #RequiredStringValidator
• #StringLengthFieldValidator
• #StringRegexValidator
• #UrlValidator
• #VisitorFieldValidator

NOTE: This is a work in progress and not yet finished!

RequiredFieldValidator

This validator checks that a field is non-null.

Example:

@RequiredFieldValidator(message = "Default message", key = "required.field", shortCircuit = true)

RequiredStringValidator

This validator checks that a String field is not empty (i.e. non-null with a length > 0).

Example:

@RequiredStringValidator(message = "Default message", key = "required.string", shortCircuit = true, trim = true)

StringLengthFieldValidator

This validator checks that a String field is of the right length. It assumes that the field is a String.

If neither minLength nor maxLength is set, nothing will be done.

Example:

@StringLengthFieldValidator(message = "Default message", key = "required.field", shortCircuit = true, trim = true, minLength = "5",  maxLength = "12")

StringRegexValidator

This validator checks that a String field matches a configure Regular Expression, if it is not an empty String.

Example:

@StringRegexValidator(message = "Default message", key = "required.field", shortCircuit = true)

EmailValidator

This validator checks that a field is a valid e-mail address if it contains a non-empty String.

Example:

@EmailValidator(message = "Default message", key = "required.field", shortCircuit = true)

UrlValidator

This validator checks that a field is a valid URL.

Example:

@UrlValidator(message = "Default message", key = "required.field", shortCircuit = true)

IntRangeFieldValidator

This validator checks that a numeric field has a value within a specified range.

If neither min nor max is set, nothing will be done.

Example:

@IntRangeFieldValidator(message = "Default message", key = "required.field", shortCircuit = true)

DateRangeFieldValidator

This validator checks that a date field has a value within a specified range.

If neither min nor max is set, nothing will be done.

Example:

@DateRangeFieldValidator(message = "Default message", key = "required.field", shortCircuit = true)

ConversionErrorFieldValidator

This validator checks if there are any conversion errors for a field and applies them if they exist. See Type Conversion Error Handling for details.

Example:

@ConversionErrorFieldValidator(message = "Default message", key = "required.field", shortCircuit = true)

ExpressionValidator

This validator uses an OGNL expression to perform its validation. The error message will be added to the action if the expression returns false when it is evaluated against the value stack.

Example:

@ExpressionValidator(message = "Default message", key = "required.field", shortCircuit = true)

FieldExpressionValidator

This validator uses an OGNL expression to perform its validation. The error message will be added to the field if the expression returns false when it is evaluated against the value stack.

Example:

@FieldExpressionValidator(message = "Default message", key = "required.field", shortCircuit = true)

VisitorFieldValidator

The validator allows you to forward validation to object properties of your action using the objects own validation files. This allows you to use the ModelDriven development pattern and manage your validations for your models in one place, where they belong, next to your model classes. The VisitorFieldValidator can handle either simple Object properties, Collections of Objects, or Arrays.

The error message for the VisitorFieldValidator will be appended in front of validation messages added by the validations for the Object message.

Example:

@VisitorFieldValidator(message = "Default message", key = "required.field", shortCircuit = true)

Here we see the context being overridden in the validator mapping, so the action alias context will not be propogated.

ModelDriven example:

@VisitorFieldValidator(message = "Default message", key = "required.field", shortCircuit = true)

This will use the model's validation rules and any errors messages will be applied directly (nothing is prefixed because of the empty message).