I would suggest using JSON if you need non-GWT clients to talk to your services. I wrote a JSON service that wraps all my (GWT-RPC) services, but it is an imperfect solution as we must avoid using Collections as parameters, not override service methods, and several other various issues.
On Apr 28, 8:37 am, JoeB <[email protected]> wrote: > How would I write a Java application client that communicates with an > existing GWT-RPC service? I'm currently designing and building a > standard GWT webapp where the client and server communicate via GWT- > RPC, but I'd like to make the server's data accessible to another > remote application to-be-built in the future. Is there an easy way to > expose a GWT-RPC service to another client, or would I be better off > switching the protocol to something like XML or JSON? (The future > client could be built using any Java-based technology, including GWT.) > > Thanks for the advice. > > -- Joe --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
