A number of times we've run into serialization exceptions with GWT-RPC. Of course following the serialization policies for GWT-RPC to the letter can prevent this, but not all of our devs are keen on these.
Since the compiler sees every RPC async interface, and is compiling those objects passed via the interface, is it possible to detect RPC serialization issues at compile time rather than runtime when it is first used? Seems like the compiler should be able to do this but I've not been able to find a setting for it. That would save folks time and make using GWT-RPC less error prone. Heck, adding it to the GWT Eclipse Plugin for automated error checking would be even more useful. Thanks for any tips or tricks you may be able to provide. :) Sincerely, Joseph -- 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/-/xDXk_IhmZyoJ. 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.
