Friday, August 31, 2018

How to write RPC services that don't inherit RemoteService?


I have a bunch of service interfaces in a jar. They don't extend RemoteService interface. Their server side implementations are currently spring remoting stubs (HttpInvokerProxyFactoryBean).

[browser side] <---RPC---> [server side] <---Spring remoting (http invoker)---> [actual service implementations with business rules and all]

I wish to use these interfaces (or their async versions) client side on GWT enabling compile time verifications. Currently I have dumb server side implementations that delegate all the calls. Like this:

public class ExampleServiceImpl implements ExampleService {
private ExampleServiceStub exampleServiceStub;
int doSomething() {
return exampleServiceStub.doSomething();

I would like to get rid of the above class. Ideas? Something better than overriding RPC.decodeRequest method? Maybe it's something that has already been done...


You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment