Hi Randy, Thanks for the detailed report. You hit a bug as nothing in HTTP prevents you from returning an entity as a result of a POST/PUT/DELETE. This has been fixed in SVN and a new current.zip is available at: http://www.restlet.org/downloads/current.zip
Note that the current.zip is a snapshot of the upcoming RC1 with all deprecated methods and classes removed. See changes log for details. Best regards, Jerome > -----Message d'origine----- > De : news [mailto:[EMAIL PROTECTED] De la part de Randy Layman > Envoyé : mardi 19 décembre 2006 14:05 > À : [email protected] > Objet : Problem with Results? > > > In our Resource objects, after processing a PUT, we use the Result's > constructor that takes a status and a representation so that > our client can get > the complete representation of the object it just put (in our > case getting the > ID value just assigned for newly created objects). Unfortunately our > representation doesn't make it back to the requesting client. > We've traced > through the code and it seems that in the Handler class, in > the handlePut (and > handlePost) the Result's Representation is never used. > > We've been able to fix this for us by copying the code from > the Handler class > into our extended handler adding the line: > > response.setEntity(result.getEntity()); > > into the handlePut method that we copied from Handler. > > Is it intentional that the Representation field of the > Result should be > ignored? If so, why? If not, is this the right way to fix > this problem? Could > it be incorporated into the RC1 release? > > Thanks, > > Randy > > >
