"""The— Source: http://stackoverflow.com/questions/4853188/unit-testing-of-gwt-requestfactory-services-without-gwttestcase/4926160#4926160RequestFactoryMagictype can be used to instantiateRequestFactoryinstances in non-GWT runtimes. […] If you implement your ownRequestTransport(perhaps based on ajava.net.HttpUrlConnectionor ApacheHttpClientlibrary), you can write console apps, bulk-query apps, or health probers using your production RequestFactory endpoints. This is a huge improvement over GWT`s old RPC system, which only supports GWT-based clients."""
> --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors
Here's what I did as an experiment:
1) Extract autobean/{shared, server}/** and requestfactory{shared,
server/testing}/** from gwt-user.jar.
1a) There are a few other build dependencies to tease out.
2) Write a RequestTransport that uses java.net.HttpUrlConnection or
the Apache HttpClient libs.
3) IIRC, there's one or two minor API incompatibilities in the
org.json APIs built into the ADK, but they're simple to fix.
Being able to put together a self-contained requestfactory-client.jar
would go a long way to improving code re-use for GWT devs who want
Android clients (and hopefully the other way around).
--
Bob Vawter
Google Web Toolkit Team
At this stage, I have it compiling but unable to parse requests on the server
> --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors