Page History

...

...

Bean-Validation Constraints

...

...

If you like to use other keys then the ones on this page, you can specify them via the attributes of a constraint.
ExtVal constraints use the attribute name validationErrorMsgKey (it isn't a rule -> for custom ExtVal constraints you can use any name you prefer) or message for BV constraints (that's a fixed rule). JPA annotations as well as annotations for JSF validators don't have a special attribute.

Detailed customization steps

In this paragraph, the different steps which are followed to resolve the message are written out for each of the 5 groups. This can be used if you want to customize the Internationalization aspect of ExtVal further more.

MessageResolver

A MessageResolver allows customizing the resolution of violation messages.

Messages for ExtVal annotation

The steps below are the lookup order for violation messages of ExtVal annotations (e.g. @Required and @Pattern) which don't delegate the validation to std. JSF validators.

The message-text or the message-key which is specified in validationErrorMsgKey of the annotation will be used to lookup the violation message. If the user didn't specify one, the default one is used and can be found in the table on top of the page. The value of it will be referenced as msgOrKey in the rest of the paragraph.

1. If the msgOrKey value contains a space, it is the literal text that is used as message.
2. The value of msgOrKey is used as the key for the message-source (e.g. a resource bundle) which is used by the MessageResolver
   (The default implementations use messageBundleBaseName and messageBundleVarName. The last one is available since ExtVal for JSF 1.2+)
3. If msgOrKey wasn't found, the convention for a custom bundle is used org.apache.myfaces.extensions.validator.custom.validation_messages.
4. The method getCustomBaseName can return a custom base name which is specified via org.apache.myfaces.extensions.validator.CUSTOM_MESSAGE_BUNDLE in web.xml.
5. The method getBaseName has to return the base name for the current validation module. In case of the annotations mentioned above it's org.apache.myfaces.extensions.validator.baseval.message.bundle.validation_messages

If there is no message available, the key surrounded with ??? is returned. If a ValidationStrategy overrides the method resolveMessage it's possible to provide a fallback message. In case of @Required the fallback message is the message of the required attribute (key: javax.faces.component.UIInput.REQUIRED - the message text depends on the custom or default resource bundle of JSF).

ExtVal annotations which delegate to JSF Validators

The message is resolved through the standard functionality of JSF. That means that the keys (javax.faces.validator.xxxx) are looked up in the message bundle defined in the faces-config file. If it can't find it there, JSF looks in the default bundle.

So ExtVal isn't responsible for resolving the message.

JPA annotations

The keys used (as value for msgOrKey) is field_reqiured or field_too_long.

If the msgOrKey value contains a space, it is the literal text that is used as message. JPA annotations don't provide an attribute for such messages. Therefore it's required to use an add-on (e.g. the virtual meta-data add-on) for using different messages for JPA based validation.

The rest is similar to the msg resolution of plain ExtVal annotations. The only differences:
getCustomBaseName returns the base name which is configured via org.apache.myfaces.extensions.validator.JPA_VALIDATION_ERROR_MESSAGES in the web.xml. As alternative to the web.xml you can provide the base-name via the global property JPA_VALIDATION_ERROR_MESSAGES

getBaseName returns org.apache.myfaces.extensions.validator.baseval.message.bundle.jpa_messages

Cross validation annotations

It's similar the the message resolution of simple ExtVal annotations. However, in this case we have a different (logical) module. So the message bundle base name of this module is org.apache.myfaces.extensions.validator.crossval.message.bundle.validation_messages. Furthermore, it's possible to have different messages for different violations. Furthermore, there might be a reverse violation message if the validation target isn't in the same page and therefore the model value is used as validation target.

Further details will be available soon.

Bean validation

The validations performed by the Bean Validation Framework are based on a completely different system than the ones by JSF itself. The validation engine of BV just returns a list of violations. By default the MessageInterpolator of BV is responsible for resolving and interpolating the messages. ExtVal suplies a special MessageInterpolator which uses an optional MessageResolver to resolve the message template for the final interpolation of the message. So the possibilities of the MessageInterpolator can be used here as well.

Further details for BV inline-messages and message keys are available in JSF 303 and the documentation of the validation provider.
The lookup steps of the MessageResolver depend on the implementation you provide. By default the MessageResolver of the core is used. So the method getCustomBaseName returns a custom base name which is specified via org.apache.myfaces.extensions.validator.CUSTOM_MESSAGE_BUNDLE in web.xml. And the method getBaseName returns org.apache.myfaces.extensions.validator.core.message.bundle.validation_messages.

(If we don't have a bv-message-key (= marked via curly braces), the MessageResolver is not used because we have an inline-message.)