Thanks for responses.
We will create own jar with LocalizableResource, Messages, Constants,
and ConstantsWithLookup for usage of the same interfaces in GWT, Swing
and server side.
With regards
Marek
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-
Hi,
Why don't you use code generation to generate the interfaces based on the
resource bundle properties files ?
That is what we do. Developers only need to define the properties and
through a Builder config in Eclipse we auto generate
the interfaces for GWT (and you could do the same to generate
On Thu, Dec 11, 2008 at 8:38 AM, Marek Gregor wrote:
> Reason why we do not want to use GWT interfaces (Constants,
> ConstantsWithLookup, Message) is that we do not want to make
> dependency on GWT (gwt-servlet.jar or gwt.user.jar) for every module
> where localization is used.
>
It would be poss
