We solved this by treating the RPC Server as a facade, calling a true "business type object". Create another facade that the Java client can interact with. Standard OO design guys...
On Aug 11, 4:13 am, Nathan Wells <nwwe...@gmail.com> wrote: > Possible, yes. > > Problematic, yes. > > The basic problem you'll run into is that GWT RPC uses a custom > version of JSON for serialization. Essentially, you would have to > recreate the GWT-RPC mechanism for your thick client, which may or may > not be difficult. I can't say how difficult, since I've never had to > do it, but I would wager that it would be easier to either > > 1) Leave GWT-RPC behind in favor of the more standard XML or JSON > methods. > 2) Forget about having a thick Java client. > > Personally, I would prefer 2, but I don't know your particular use > case. > > On Aug 10, 9:39 pm, steven a <ira...@gmail.com> wrote: > > > > > Hi, > > > Is it possible to call the GWT RPC Server from an remote Java client, > > instead of from GWT client? > > > -steve- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
