Re: Interface hierarchy of *Async interfaces

First I want to say that it is very likely that GWT-RPC will not work anymore with GWT 3.0 so you might want to choose something different.

Next your method 

void load(Serializable identifier, AsyncCallback<B> callback);

is pretty bad with GWT-RPC. The reason is that GWT-RPC generates serializer/deserializer classes for everything that might go over the wire. If you now choose a parameter of type Serializable then GWT will generate serializer/deserializer classes for every serializable class even if your app doesn't use most of them. So with GWT-RPC you usually try to be as specific as possible and only use broad interfaces if you know you will send most of its implementations anyways. This gives an indication that GWT-RPC itself has some design flaws, even though it is super convenient to use.

So maybe you want to rethink your approach a bit.

But regarding your question: As you are talking about a Util class it sounds like you are generating async interfaces via Maven GWT plugin. In that case you can only change the generated async output by forking the gwt-maven-plugin and modify:

https://github.com/gwt-maven-plugin/gwt-maven-plugin/blob/master/src/main/java/org/codehaus/mojo/gwt/GenerateAsyncMojo.java

or by not using the generateAsync goal at all and write your own code generator.

-- J.

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.