Hello, I am looking to start a GWT client project to build a front end to our existing REST (JAX-RS/Stateless) backend system.
I am very interested in the power and plumbing that was described at Google IO relating to GWT 2.1 and the RequestFactory architecture (with its caches etc) So I will be building the GWT <-> JAX-RS stuff by hand. My question is should I use GWTs own RPC mechanisms and have a servlet on the backend integrate with my service layer or talk to my JAX-RS endpoints or is there a way to leverage the power of RequestFactory with a REST Client in GWT itself. I have looked at Restlet, RestyGWT etc... but they require a lot of plumbing code - I already have DTOs from JAX-RS on my side I would like GWT to use I am aware of Spring Roo aswell but ties into the persistent layer too much - It would be great to have it simply as a scaffolding mechanism for GWT (i.e. generate from existing DTOs - I see one of the most requested features for Roo it to build from an existing entity model - but we have our JAX-RS layer - we want to build GWT from that!) Any architectural suggestions welcome, from what I have seen so far using GWT with its own RPC->Servlet mechanism is probably a lot less painful than my preferred GWT->JAX-RS approach. -A -- 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-tool...@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.
