Hi, there is no problem in using a custom object, the characteristic of the examples with collections or maps is that they TEST the use of Generics: the generic parameter must be reused correctly in the Async interface. I've added a new example with a CustomObject to the asynchronize-example project to show that using a custom object is not a problem.
Please consider that the processor only generates the interface, but then it need to be used with a real RPC implementation like GWT RPC. I am considering to release an RPC implementation library based on HTTP and GSON, but it is pure Java, it works with Android but it does not work with GWT (we use the same async interface both on the Android client and GWT client, so we can better reuse code logic and handle with the same code the (asynchronous) requests to the server), but I do not foreseen to release it soon... Regards, Cristiano Il giorno martedì 15 settembre 2015 14:37:53 UTC+2, Lars ha scritto: > > All your samples deal with primitive stuff or collections of this. For a > real RPC we need custom objects as well and a way to transfer them, but as > I see it right now you generate only the async interface?! -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/5b36f100-ff32-4bff-9f49-eeafd175f694%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
