i18n-ing server-side validation error messages

[csillag]

Sometimes there are situations when some validation only happens on the server side, and not on the client side.

In these cases, the error messages will be generated on the server side.

Currently, SmartClient's (and thus SmartGWT's) i18n system only affects the client side.

Is there a way to i18n the server-side validation messages, too?

[Metallic]

Sometimes there are situations when some validation only happens on the server side, and not on the client side.

In these cases, the error messages will be generated on the server side.

Currently, SmartClient's (and thus SmartGWT's) i18n system only affects the client side.

Is there a way to i18n the server-side validation messages, too?

There are two ways:

1) For each request in additional parameter you will pass current locale, and implement i18n in serverside.
2) The other way - is to use error constants and pass them into client. For each constant there will be i18nized message

Second way is more preferable, because you can create gwt module on serverside and share constants between server and client side, also you don't need to implement i18n in server.

[Blama]

Is there a way to i18n the server-side validation messages, too?

Anyone hitting this thread, see this post.

Best regards
Blama

[carlossierra]

For a cleaner example provided also by Blama, take a look at this thread:
http://forums.smartclient.com/forum/...side-dsrequest