Hi Hez, Actually, it is documented, although perhaps not as loudly or prominently as it should. I'll look into ways of changing that.
Serializable Types (see Polymorphism section): http://code.google.com/webtoolkit/doc/1.6/DevGuideServerCommunication.html#DevGuideSerializableTypes <http://code.google.com/webtoolkit/doc/1.6/DevGuideServerCommunication.html#DevGuideSerializableTypes> Cheers, -Sumit Chandel On Sun, Aug 9, 2009 at 2:39 AM, hezjing <[email protected]> wrote: > Uh-huh ... thanks for your explanation,and I think this piece of > information is worth mention in the GWT's developer's guide too! > > On Sun, Aug 9, 2009 at 5:46 AM, pohl <[email protected]> wrote: > >> >> To add to Paul's answer: the practice that Ray Ryan advocated is not >> to prevent GWT-RPC from picking up the wrong implementation. >> >> Rather, it is to prevent GWT-RPC from including all possible >> implementations, even those that you will never use. >> >> For example, if you use List<X> the GWT-RPC magic-generator will have >> to include compiled javascript that implements java.util.Vector class, >> because it will have no way of knowing that the server will never >> return such a type. >> >> So being specific with ArrayList<X> keeps the size of your compiled >> javascript as small as possible. >> >> > > > -- > > Hez > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. 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 -~----------~----~----~----~------~----~------~--~---
