Here is what I would do : 1) refactor your business logic (which usually returns a Serializeable object) out of the GWT RemoteServeiceServelt,
2) Create some normal Java servelet with the API style of your choosing, REST or not. 3) Call your business logic from both places, GWT just return the objects, New JSON based API run JSON serializing before returning the result (use a json serializer of course) (of course with exception handling as well). That way your backend needs some small amount of change and you can keep your business logic in one place to be used by two frontend. On Wed, Dec 3, 2014 at 10:16 AM, Magnus <[email protected]> wrote: > Hi! > >> If I'd start the project today, I'd just use plain REST / JSON for both >> the desktop and mobile versions. > > > Ok, but how can you do REST/JSON with a GWT application? > Would you replace the RPC calls with REST requests, using a servlet or what? > > Thanks > Magnus > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
