Sounds good. We will use top level classes to store the enums and sourced
them in the gwt.xml module.
Thanks a lot for your replies!
Ido
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To view this discussion on the web visit
https://gr
No, Enums have to be available on the client-side. If you have them as
top-level classes, or if their containing class is "translatable", then you
can easily make them accessible to the client-side using a gwt.xml module
with a in it (with
one per file defining an Enum).
That's what we're doi
Thanks for the reply.
We indeed created new gwt module which contains RF classes. Our RF module
contains proxies, services and servlet to populate Spring services through
RF.
Then we have other gwt projects then import the above RF module. we can't
really import the packages with the enum defi
I believe you have already converted your existing code into a gwt module.
(With that this is not possible) and finally in the module's gwt.xml file
include the path of the package which contains the enum.
Then it will be available on the client code!
Hope this helps!
--
You received this m
Hi all,
We've been trying to find a way to transfer enums to client side.
David Chandler (
http://turbomanage.wordpress.com/2011/03/25/using-gwt-requestfactory-with-objectify/)
made it by defining enums in the proxy.
Our case is a bit different, my team has to setup a RequestFactory layer
abov
