Your underlying service could be just about anything, but use the RemoteServiceServlet to expose that service to GWT via RPC then SOAP or JSON or whatever to expose it to non-GWT clients.
Basically you use the RemoteServiceServlet to handle object serialization and just pass the objects on to your actual implementation. Same idea for your other protocol(s). RPC is particularly handy for GWT clients, but would be a bit tweaky (and fragile) to implement in non-GWT clients. -jason On Apr 28, 2009, at 6:37 AM, JoeB 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 -~----------~----~----~----~------~----~------~--~---
