> GWT already checks it (although error messages might not be perfect all > the time). And in case something isn't checked correctly, it should be > implemented into GWT itself. >
That was also my expectation, but we sometimes run into serialization errors at run time even though GWT compilation completed. Often it is caused by simple cases like a transfer class without default constructor or a serializable interface in our core without an implementation in our core modules. (we have optional modules that are not deployed on all systems). I would like to catch those at compile time and break the build. No one sees the warnings in that deeply indented output. I guess the correct approach then is to look into SerializableTypeOracleBuilder and friends and see if I can find out why they slip through. Looking forward to 2.7. I will try to find some time to evaluate the snapshot build. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
