I try to use the classvalidator in our project with a server and a swing client.

My problem comes with i18n of the messages. Messages from the server are in the language of the default locale of the server.
A solution could be a getMessage(string language) method on InvalidValue.
The languages could be restricted by overwriting the ValidatorMessages.properties or providing a custom bundle, throw away the unused.

Any ideas?

Bart

An elegant solution to translate the fieldName is also welcome, but that's treated in another thread.

You can implement a MessageInterpolator that can deal with that, I think

A MessageInterpolator returns 1 String, the message. I could construct a long string with all languages in, and parse it when needed but that's not very robust.
If I could provide my own InvalidValue (with x messages) and intervene in some way in the validation (like MessageInterpolator), I could construct the Invalidvalue that is returned by the validator.

I was thinking that MessageInterpolator could retrieve the right Locale (for example set to a threadlocal by your application), to build the right message right away.

In the project , we're using Spring's HttpInvoker for the remote calls. The language of the client can be switched as the user wants, it's not stored in the DB.
To know the language at the server means that the language should be added to each call.

For now , in this client, we validate twice, once before the call (thus in the client locale) and on the server before saving.
It's a solution for this project.

Apparently there's no other way to solve it then by the messageinterpolator. I hope future releases bring more possibilities (and a way to translate the fieldname).

thanks for the reactions.

Bart

But the messageInterpolator solution work and does not seem to be that hard to implement, is it?

It works, if the locale is added to each call to the server.
But in that case I could set it as default and there would be no need for a MessageInterpolator.
My question was how to do it without knowing the language in advance.

If the MessageInterpolator read the Locale from a threadlocal variable that is set by your code right before validating, you have what you want