Different return type in the ServiceAssync interface?

[alex.d]

I have different return type (Request instead of void) in my ServiceAssync interface for several functions. Issue: every time i add new function to the interface, ServiceAssync is generated again replacing Request with void. Is it possible to avoid this?

[Eric Clayberg]

I have different return type (Request instead of void) in my ServiceAssync interface for several functions. Issue: every time i add new function to the interface, ServiceAssync is generated again replacing Request with void. Is it possible to avoid this?

In the latest build, you can now add a @wbp.gwt.Request JavaDoc tag to have the async method generated to return a Request.

For example:

Code: Select all

    /**
     * @wbp.gwt.Request
     */
    int bar();

will generate:

Code: Select all

    Request bar(AsyncCallback<Integer> callback);