Hi guys,

Which version of Restlet are you using? We fixed some related issues in
Restlet edition for GWT in version 2.0 M5.

Best regards,
Jerome Louvel
--
Restlet ~ Founder and Lead developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com



-----Message d'origine-----
De : Daniel Bell [mailto:db...@itree.com.au] 
Envoyé : mardi 6 octobre 2009 02:34
À : discuss@restlet.tigris.org
Objet : RE: OPTIONS instead of POST on GWT

I had the same problem. We actually ended up using the GWT request builder
instead, and created new Methods for it (PUT and DELETE) to use with our
Restlet on the server.

-----Original Message-----
From: webp...@tigris.org [mailto:webp...@tigris.org]
Sent: Monday, 5 October 2009 8:25 PM
To: discuss@restlet.tigris.org
Subject: OPTIONS instead of POST on GWT

Hi,

   I'm a new user of Restlet. I want to call from a GWT client a REST
service running on GAE. This is my client code:

Client client = new Client(Protocol.HTTP);
        client.post("http://localhost:4040/ping";,
getXMLCourseRepresentation(),new Uniform() {
                        @Override
                        public void handle(Request request, Response
response,  Uniform callback) {
}
        });

I'm doing a local test and I'm running the client on tomcat and the GAE
server on hosted mode. I don't understand why using the post method from the
client always call the HTTP OPTIONS method and not the POST.

Any clue? I'm begining to get desperate...

Thanks

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=24034
94

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=24039
22

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2404843

Reply via email to