Testing GWT RPC services

@RemoteServiceRelativePath("greet")
public interface GreetingService extends RemoteService {
  String greetServer(String name);
}

public class GreetingServiceTest extends TestCase{
  private static GreetingService rpcService =
    SyncProxy.newProxyInstance(GreetingService.class,
          "http://localhost/helloApp", "greet");

  public void testGreeting() {
    String result = rpcService.greetServer("SyncProxy");
    assertTrue((result != null) && (result.startsWith("Hello, SyncProxy")))
  }
}

GreetingServiceAsync rpcServiceAsync =
SyncProxy.newProxyInstance(GreetingServiceAsync.class,
          "http://localhost/helloApp", "greet");

rpcService.greetServer("SyncProxy", new AsyncCallback<String>(){
  public void onFailure(Throwable caught) {
    ...
  }
  public void onSuccess(String result) {
    ...
  }
});

59 Responses to “Testing GWT RPC services”

1. Piotr Szaranski says:

   May 18, 2010 at 4:31 pm

   Thx for reply, i have another question now

   In our webApp we have resources with constrained access – standard form based authentication, which means we have to first login using POST and then we can use GWT services.

   This means in our integration tests we need to first login with POST (using httpclient for example), grab the cookies returned after authentication and push them inside CookieManager in RemoteServiceSyncProxy.

   Is there any possibility to achieve this without using reflection? Probably not, but its always better to ask first…
2. Piotr Szaranski says:

   May 18, 2010 at 6:03 pm

   Method getDomainFromHost in class CookieManager makes some ugly work with doted hosts, for example:
   192.168.0.1 -> 168.0.1

   I think it is not a desired behavior
3. ricardo says:

   May 21, 2010 at 10:29 am

   Trung, thanks a lot for this great tool.

   I’ll share my experience. I use objectify and my types were not being sent from the server, I was getting “type was not assignable” serialization exceptions. I had to:
   -Initizalize my service in a slightly different way, as: myService = (MyService) SyncProxy.newProxyInstance(MyService.class,
   “http://127.0.0.1:8888/my_app/”, “my_serv”);
   -Copy my .gwt.rpc file to “null.gwt.rpc”, since the strongname that the server receives when the call comes from the test class is “null”

   And it works…
4. m.w.e. says:

   May 29, 2010 at 6:13 am

   I use sync proxy with junit. Make sure to set fork=yes in the junit task. Syncproxy was not picking up the correct classpath without it.
5. yusuf says:

   June 7, 2010 at 11:06 am

   Hi,

   i get this error
   java.lang.NoClassDefFoundError: com/google/gdata/client/GoogleAuthTokenFactory
   at de.megapharm.mm.web.testdata.RPCServiceTest.(RPCServiceTest.java:30)

   Have you a idea ?
   Thank You
6. Trung says:

   June 10, 2010 at 5:47 am

   SyncProxy depends in gdata java client, thus download it from code.google.com

   Hope this help
7. Amos says:

   July 19, 2010 at 3:24 am

   First, thanks for some great software. This is great to have.

   Here are collection of notes I had to go through to get this to work (including notes from people here):

   1. Get the Google Code libraries
   ———————————–
   http://code.google.com/p/gdata-java-client/downloads/list
   You want the Google Data java client.
   Add the jar file: jdata-core-1.0.jar to your classpath (or latest version)

   2. Change the Example (as Ricardo mentions above)
   ———————————————–
   A “/” is missing between the base URL and the service name.
   (MyService.class, “http://127.0.0.1:8888/my_app/”, “my_serv”); (note the “/” after my_app)

   3. Serialization Policy
   ————————————
   - Some classes will not serialize without the IsSerializable interface (although GWT doesn’t require it). Just add them.
   - In order to serialize a class to/from a service, it must appear in at least one method of the service both as input and output.
   - Example: MyClass dummyMethod(MyClass input);
   - Without the above, either serialization or deserialization will fail.
   - For example: void myMethod(MyInputClass input)
   – In this case, serialization will fail because the serialization policy only expects to deserialize the class and the serialization on the client side will fail.
   - If you see serialization policy exceptions you may want to follow this step.

   4. Add the GWT application directory to classpath
   —————————————–
   The GWT compiled files directory is required for proper serialization. The directory contains multiple files like this: 694BD6C5E9CCB9810670C827B93E270A.gwt.rpc and other files of type *.gwt.rpc, *.cache.png, *.cache.html

   The files of type *.gwt.rpc are the serialization policy for your classes and without this directory on the classpath the serialization will fail.

   Also, note that the files are only updated after you compile the GWT client files. The eclipse (IDE) compilation does not update these files.
8. Ora Finona says:

   August 4, 2010 at 7:33 am

   This is a bit off discussion, which I apologize for, but would you and your readers mind giving your thoughts about the recent oil spill, you’re opinion seriously helps and I can’t thank you enough for taking a few moments to give it. I left the URL in the appropriate field, thanks!
9. Colin says:

   August 11, 2010 at 9:35 pm

   @Piotr Szaranski:

   I had the same issue with authentication, and I also was looking for more robust session management. I logged:

   http://code.google.com/p/gwt-syncproxy/issues/detail?id=6

   with an attached patch that while perhaps still a little rough around the edges provides support for plugging in login code.