Tapestry provides its own MessageInterpolator which is the wrapper around
the default one. Tapestry's interpolator is using ThreadLocale#getLocale()
in MessageInterpolator#interpolate without Locale parameter. Check this out.

https://svn.apache.org/repos/asf/tapestry/tapestry5/trunk/tapestry-beanvalidator/src/main/java/org/apache/tapestry5/internal/beanvalidator/MessageInterpolatorImpl.java

I guess the problem is that you didn't place the translations into a file
expected by the Bean Validation API. So far only these files are supported,
Tapestry's message catalog not.

On Mon, Mar 5, 2012 at 6:46 PM, Christian Köberl <
tapestry.christian.koeb...@gmail.com> wrote:

> There seems to be a bug in the localization of the bean validation error
> messages.
>
> When I start my server locale is "de" and the client locale is "en" the
> message is displayed in German "First Name kann nicht null sein".
>
> I guess the bug is in BeanFieldValidator#interpolateMessage - this calls
> MessageInterpolator#interpolate without the current Locale, there's
> another method with the additional Locale parameter.
>
> Should I file a JIRA?
>
> --
> Chris
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>


-- 
Best regards,

Igor Drobiazko
http://tapestry5.de
http://twitter.com/drobiazko

Reply via email to