[
http://opensource.atlassian.com/projects/hibernate/browse/HV-44?page=com....
]
Jean-Christian Gagné commented on HV-44:
----------------------------------------
I would make 2 suggestions :
1) Create new methods in ClassValidator, adding a Locale parameter to all
getInvalidValues(...).
2) I agree that custom config may be neccessary to introduce a Locale resolving strategy,
but providing its own MessageInterpolator is not a simple solution for a not-so-unusual
problem. So I suggest to introduce a simple LocaleResolver interface in Hibernate
validator configuration, with default returning Locale.getDefault().
Make Hibernate Validator multi-lingual
--------------------------------------
Key: HV-44
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HV-44
Project: Hibernate Validator
Issue Type: Improvement
Affects Versions: 3.0.0.ga
Reporter: Olle Hallin
Hibernate Validator 3.0.0 is unfortunately useless in a multi-lingual web app, since it
uses Locale.getDefault() for locating the validation message bundle.
Each and every HTTP request can have a different locale, in it's own thread.
Please add something in line with Spring's LocaleContextHolder (a ThreadLocal), which
can be set early in the request handling chain. If not set, it could fall back to the
platform's Locale.getDefault().
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira