Comments for GWT Developer's Tools

Comment on Apache Shiro on AppEngine by Dominik

Dominik — Sun, 31 Jul 2011 15:11:21 +0000

Thank you for the post.

I am quite a noob but as I understand it, this tutorial adds Shiro on top of the Users service. Does this mean that everyone still logs in with their google accounts?

Actually I was looking for a tutorial that would show how to use Apache Shiro and GAE to build your own user db (in the datastore). With people having to register and then login. Can someone point me to a tutorial like that? I haven’t found anything, yet.

Comment on Testing GWT RPC services by Ben

Ben — Thu, 21 Jul 2011 13:58:29 +0000

I’ve just tried using this against GWT 2.3 and got an error “Expecting version 6 from server, got 7″. I’ve managed to recompile from source and it’s resolved that issue and left me with the following:
com.google.gwt.user.client.rpc.InvocationException: Exception while invoking the remote service au.com.cgu.harvest.web.client.request.IRequestDispatcherService.dispatch
at com.gdevelop.gwt.syncrpc.RemoteServiceInvocationHandler.invoke(RemoteServiceInvocationHandler.java:194)
at $Proxy36.dispatch(Unknown Source)
at au.com.cgu.harvest.transaction.JettyTest.startJetty(JettyTest.java:91)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException: Type ‘au.com.cgu.harvest.request.RetrieveDocumentRequest’ was not assignable to ‘com.google.gwt.user.client.rpc.IsSerializable’ and did not have a custom field serializer. For security purposes, this type will not be deserialized.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at com.gdevelop.gwt.syncrpc.SyncClientSerializationStreamReader.instantiate(SyncClientSerializationStreamReader.java:519)
at com.gdevelop.gwt.syncrpc.SyncClientSerializationStreamReader.deserialize(SyncClientSerializationStreamReader.java:372)
at com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.readObject(AbstractSerializationStreamReader.java:119)
at com.gdevelop.gwt.syncrpc.RemoteServiceSyncProxy.doInvoke(RemoteServiceSyncProxy.java:165)
at com.gdevelop.gwt.syncrpc.RemoteServiceInvocationHandler.invoke(RemoteServiceInvocationHandler.java:173)
… 24 more

I have confirmed that my *.gwt.rpc is on the classpath (and have tried renaming it to null as a previous post suggested).

I’m now attempting to get the tests (from svn) to compile so I can work through this issue but can’t work out what the gwt-dev-? dependency is for all tests in the com.gdevelop.gwt.syncrpc.test package.

Please point me in the right direction if you can. Happy to contribute patches back

Ben.

Comment on Invoke GWT RPC services deployed on Google App Engine by jogo

jogo — Mon, 13 Jun 2011 20:19:46 +0000

First of all, great work! I’m trying to invoke remote service on GAE (greetServer), but no luck.

Which version of GWT is SyncProxy compatible with? I’m using the latest version of GWT (2.3.0) and I see some serialization exceptions in the log.

Comment on Testing GWT RPC services by Anoop John

Anoop John — Thu, 09 Jun 2011 06:23:14 +0000

Hi,
This is really cool. But i have a problem. I created a GWT application in eclipse and success fully executed with default server. I tried to deploy in tomcat5 server and tried to access the remote method from my java application. This is failed. Please help me to find out the reason. I got the following error:

com.google.gwt.user.client.rpc.InvocationException: Exception while invoking the remote service anoop.web_service.client.GreetingService.greetServer
at com.gdevelop.gwt.syncrpc.RemoteServiceInvocationHandler.invoke(RemoteServiceInvocationHandler.java:185)
at $Proxy0.greetServer(Unknown Source)
at anoop.web_service.client.AppMain.main(AppMain.java:19)
Caused by: com.google.gwt.user.client.rpc.InvocationException: IOException
at com.gdevelop.gwt.syncrpc.RemoteServiceSyncProxy.doInvoke(RemoteServiceSyncProxy.java:167)
at com.gdevelop.gwt.syncrpc.RemoteServiceInvocationHandler.invoke(RemoteServiceInvocationHandler.java:164)
… 2 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.net.NetworkClient.doConnect(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
at com.gdevelop.gwt.syncrpc.RemoteServiceSyncProxy.doInvoke(RemoteServiceSyncProxy.java:133)
… 3 more

Comment on Testing GWT RPC services by Ian Jones

Ian Jones — Wed, 30 Mar 2011 12:14:11 +0000

Hi Trung,

I’ve just started using syncproxy and it works great. I’m trying to use it with GWTEventService, and for some reason the the gwt.rpc file says it can’t deserialize one of the classes returned by the service (DefaultDomainEvent). I checked out your code so I could ignore the deserialization error, only to find that you’ve already done it in revision 23. Any ideas when this change will be released?
Many thanks, and great work,
Ian

Comment on Testing GWT RPC services by Julian Schillinger

Julian Schillinger — Mon, 28 Feb 2011 17:10:28 +0000

Hi,

I have the same problem and am unable to solve it, unless I change false to true in the gwt.rpc files I copy to the SyncProxy client. This results in the serialization policy error showing on the server (which works with the unmodified files) rather than the client.

Did anyone find a solution to this?

Thanks,
Julian

Comment on Testing GWT RPC services by aj wecker

aj wecker — Sun, 27 Feb 2011 10:13:44 +0000

For some reason need to double the app name
so change path to webfrontend/PILSERVICE

Comment on Testing GWT RPC services by aj wecker

aj wecker — Sun, 27 Feb 2011 07:13:00 +0000

I can run on the Eclipse jetty server port 8888 fine
domain= http://localhost:8888/webfrontend/
path=PILService
(this is after I added a servlet tag to my webfrontend.gwt.xml file
However when I try to run on Apache 8080
I get a FileNotFoundException
my web.xml looks like this:

[web-app]

[!-- Servlets --]
[servlet]
[servlet-name]PILServiceServlet[/servlet-name]
[servlet-class]il.ac.haifa.pil.webfrontend.server.PilServiceImpl[/servlet-class]
[/servlet]

[servlet-mapping]
[servlet-name>PILServiceServlet[/servlet-name]
[url-pattern]/webfrontend/PILService[/url-pattern]
[/servlet-mapping>

[!-- Default page to serve --]
[welcome-file-list]
[welcome-file]WebFrontEnd.html[/welcome-file]
[/welcome-file-list]

[/web-app]

Any suggestions
Thanks

Comment on Testing GWT RPC services by Amol

Amol — Tue, 01 Feb 2011 11:51:19 +0000

Hello,

Is there any testing tool which will test the GWT RPC. In my application we are building the services first and need to test the services before integrating to UI, can someone help?

Regards,
Amol

Comment on Apache Shiro on AppEngine by Les Hazlewood

Les Hazlewood — Tue, 04 Jan 2011 18:13:07 +0000

Hi Trung,

This is a great post and very useful for GAE users. Thanks for sharing!

Cheers,

Les