Jerome, I attempted to make use of this version without my customization to the JaxbConverter at it was unsuccessful. It returns to the previous error behavior attempting to parse the JSON submitted on Request as XML.
> Hi Michael, > > Is your conversion problem occurring for the request entity, or for the > response one? > > In the former case, we have fixed a bug post-RC3 on this front. Could you > try again with this snapshot and confirm? > http://www.restlet.org/downloads/2.1/restlet-jee-2.1snapshot.zip > > Best regards, > Jerome > -- > http://www.restlet.com > http://twitter.com/#!/jlouvel > > > -----Message d'origine----- > De : Michael Henderson [mailto:dillius at gmail dot com] > Envoyé : mercredi 21 mars 2012 21:41 > À : discuss at restlet dot tigris dot org > Objet : RE: Re: ConverterService behavior differs on GET and PUT > > The main thing that caught me off guard was the lack of real consideration > of the HTTP headers for determining the converter to be used. Though I may > be incorrect in this belief, as I have not gone through the Restlet code > base enough to know for sure that it is not being considered for the > purposes of choosing the Representation type to be passed in. > > > > Wow, scoring converters is a delicate business! I understand a new > > approach is in the works, though. > > > > I replace the out-of-the-box Jackson and Freemarker converters with my > > own custom versions for other reasons, but a side benefit was that I > > can prevent scoring surprises like the one you encountered. > > > > --tim > > > > ------------------------------------------------------ > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=29383 > 95 ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2938830
