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 <source path=""><include name="Status.java" /></source> in it (with one <include/> per file defining an Enum). That's what we're doing and it works great.
If your Enums are nested and the containing class is not translatable, then you'll have to provide an "emulated" version of your Enums and containing classes, using a <super-source/> in your module pointing to a subfolder where you'll put your emulated classes (the containing class would be empty, serving only as a container, and you'll copy your Enum definition there; the GWT Compiler –thus, the client-side code– would use the "super-source", whereas the server-side code would use the actual classes). -- 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://groups.google.com/d/msg/google-web-toolkit/-/L5IfzuP7FTsJ. 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.
