This is (partly) what RequestFactory tries to solve (vs. GWT-RPC): you no longer use your server-side classes on the client-side, so you don't have the issues of your entities having to be "translatable" by the GWT compiler.
If you work with JSON (using things like Jackson or GSON on the server-side), you can use AutoBeans on the client-side (you can also use them on the server-side, btw) to easily parse and manipulate the objects (at least a bit more easily than with JsonUtils.safeEval() and JS Overlay Types). But if you only add annotations to your classes, there's no reason you couldn't use them on the client-side too; you just have to make sure you have the source code for the annotations on the classpath too. Just a suggestion; AutoBean and RequestFactory are not a silver-bullet, and JSOs and GWT-RPC are still viable choices (FYI, Google Groups uses GWT-RPC). -- 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/-/0UmyquSlTucJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
