Hi Mathieu, Thanks for the update. The easiest way to detect such things is to check the server log for the given request. By default the go in the console, with URI and status code. 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 : [email protected] [mailto:[email protected]] Envoyé : vendredi 17 avril 2009 15:56 À : [email protected] Objet : RE: Entity not set when setting it from storeRepresentation Hi Jerome, Well, I think I solved this one. Here is what happened : - I had an exception within the XML parsing to persist the resource (sorry I did not include this part, I thought it was not the source of the problem) - This exception was caught by the catch block, and rethrown as a ResourceException - I think this leads to an empty representation on client side, because (I did not check that, but I'm pretty sure...) it sends back an empty HTTP message with a HTTP-500 response code I'm sorry for this. It was my error. But one question still : Is there something I could've done on client side (server side maybe also...) to detect that the server could not handle the request? Is it solved only by the means of response code? Or is there something in the Restlet framework that could tell the client code that something came wrong? Thanks in advance, Mathieu ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=17682 59 ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1909038
