thanks for the reply. That serialization problem makes sense.
On 9 Jan., 00:11, Richard Vowles <
richard.vow...@gmail.com> wrote:
> The problem with talking to your GWT services via Android is that you are
> effectively using serialization. If you server objects change, your client
> ones need to as well. This is fine with GWT as its just a webpage - chances
> are you deploy them together. Thats not true with Android - its a different
> app and as with Java serialization, there is no easy way to make sure they
> evolve together. Thats why most people go the JSON route when dealing with
> Android/GWT/GAE.
>
> Unfortunately (or fortunately, depending on your POV), I did go down this
> track before swapping back to JSON (and Restlet is awful, I can't stand it,
> as i tried it before swapping back to Jersey). and got GWT dispatch working
> against Android for a GWT service. It is a fork of another persons project
> who hadn't structured their maven project in a manner I would consider well
> designed and reusable so I needed to do this. If you still need to do this
> given the problems, let me know and I'll put it up on github (I am going
> away for a few days tho, so this may take me a few days to achieve).
>
> Richard
>