(1) The problem with the OP's code was that he had the getClients() method in the async class take an AsyncCallback<String> but the non-async interface returned an ArrayList<String>. If you want to return an ArrayList of strings, then the callback should have been AsyncCallback<ArrayList<String>>
(2) ArrayList<String> is better than List<String> in GWT RPC interfaces because if you use List<String>, then the GWT compiler must search for every implementation of List and spend time looking at whether it's used/making the serialization code for it. At the very least, compilation is faster if you stick to the most specific declaration you can. It may also generate less javascript. Paul Trevis wrote: > Not to complicate matters but using ArrayList instead od List supposed > to be better in gwt? I could have sworn that ray ryan alluded to this > in his presentation. > > I still don't do it because I hate seeing that in my code but still, > ymmv > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
