Dear All,
i am using hibernate validation + JSR 303 validation with JSF 2 and RichFaces 4

when i add annotations on my bean attributes, i get the messages from the ValidationMessages.properties on the default (root) package, assume the case as folllow:

class MyBean{
@NotEmpty(message="{Name_Error_Message}")
private String name;
// rest of code here
}

ValidationMessages.properties
Name_Error_Message = The name cannot be empty

my question is: can i change the name of the ValidationMessages.properties to any name i want? if yes, HOW?

Regards.

Mohd Noor

Hi,

Yes you can :)

To do that you have to write your own MessageInterpolator which delegates the message interpolation to Hibernate Validator ResourceBundleMessageInterpolator. This ResourceBundleMessageInterpolator have to be initialized with a custom ResourceBundleLocator or with an implementation provided by HV (see [1]). This ResourceBundleLocator will be responsible to locate your custom ResourceBundle. After you'll have to create a validation configuration file named validation.xml[2] which references your custom MessageInterpolator implementation class.

Hope this help

--Kevin

PS: For Hibernate Validator related questions please use this forum viewforum.php?f=9

[1] http://docs.jboss.org/hibernate/validat ... le-locator
[2] http://docs.jboss.org/hibernate/validat ... e/#d0e2053
[3] This post might help viewtopic.php?f=9&t=1010033

@kevin,
I think we could offer a property in Hibernate Validator to point to the filename as it's likely a common enough use case and writing a new interpolator is a bit overkill for this.

I've created https://hibernate.onjira.com/browse/HV-507

Actually it's not necessary to implement a new message interpolator. Using HV's ResourceBundleMessageInterpolator and its bundle locator API a custom bundle name can be specified like this:


This doen't work using the XML configuration at the moment, though. I generally like the property approach, but I'm slightly concerned about possible inconsistent configurations (specifying the property but using a different message interpolator etc.).

--Gunnar