Just use the regular java way to look up the exception message & throw it. Don't understand your problem.
On Wed, Apr 22, 2009 at 9:45 AM, olel <lauri...@engram.de> wrote: > > > Explain again why the name of objects can't be internalized using > constants > > on the client side? > > Maybe that was a bad example. It's easier to explain with exceptions > (defined in my application). Exceptions have an errortext that should > be internationalized as well. As exceptions are thrown at the server > and catch on the client, they are used in all architectural layers. So > I cannot use java.util.ResourceBundle as GWT would throw an error (No > source code is available for type java.util.ResourceBundle). > On the other hand I cannot use the GWT constants interface either as I > must not use client code (or client libs) on the server where the > exceptions are defined. > > > Anyways, the general solution would be to set the internationalized > string > > using java resource bundles in the server code prior to sending the > objects > > over the wire to the client code. > > Please explain that to me. How should I set the string? Do you think > of some kind of client class that sets all the strings in all server > classes that has to be internationalized? That would look crude to me. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
