It seems that we skipped this question. For tracking/archiving purpose, here are some answers:
1. This works exactly like for GWT-RPC proxies. What matters here is the HTTP method associated to the annotated Java method and the in/out parameters and how they are serialized so the server-side can handle them properly. The contract is the REST API expressed by both the synchronous ContactResource and the asynchronous ContactResourceProxy one. 2. Good point, this should be fixed. Just entered a report: http://restlet.tigris.org/issues/show_bug.cgi?id=1169 Best regards, Jerome -- Restlet ~ Founder and Technical Lead ~ http://www.restlet.org Noelios Technologies ~ http://www.noelios.com -----Message d'origine----- De : [email protected] [mailto:[email protected]] Envoyé : jeudi 3 juin 2010 19:43 À : [email protected] Objet : Question on GWT-Restlet-GAE I have downloaded your Serialization(Contact address) example and test it. I have a couple of confusion if you could help me out: 1. The ContactResourceProxy doesn't implement/inherit from the ContactResource Interface, which is implemented by the ContactServerResource. How does the framework know that ContactResourceProxy is connected to ContactResource? (through naming convention?) 2. In the example, the store function in server is annotated with @post, @Post public void store(Contact contact) { ContactServerResource.contact = contact; } and the store function in ContactResource and ContactResourceProxy is annotated with @put: @Put public void store(Contact contact); and @Put public void store(Contact contact, Result<Void> callback); However, the sample app would route the put request to the post request. I tried to pin-point the flow in code through debugger and was not successful. ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2616495 ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2652216
