Hello Thierry, sadly I have to "refloat" this bug on Restlet 2.0.1. I'm using Restlet 2.0.1 SE and PROPFIND is not handled anymore. I've switched libs back to 2.0.0 ones (which have other problems, so I cannot use 'em as a 'fix') and PROPFIND is handled properly. I switch back to 2.0.1 libs and PROPFIND is never handled.
The method's signature is this one: @Propfind public Representation propfind(Representation entity) throws ResourceException and it's never called with 2.0.1 libs, while it's properly called with 2.0.0 libs. So, it seems that 2.0.1 re-introduced the converter service bug avoiding proper handling of PROPFIND (and possibly other non-HTTP methods). Thanks in advance for fixing it for a possible release of a 2.0.2 version of restlet (will there be any? when?) On Wed, Sep 8, 2010 at 5:53 AM, Thierry Boileau <[email protected]> wrote: > Hello Fabian, > > >>So I guess I can just ommit the final DomRepresentation ... line. > Actually, as you need to access the DOM nodes, you still have to wrap the > given instance of InputRepresentation. > And as you rely on the XML extension, which provides is own converter, I > think you can try : > public Representation propfind(DomRepresentation reqrep) throws > ResourceException { > } > >>Maybe the empty parameters signature is confusing the content negotiation >>logic for the annotated method handler somehow? > Yes, this is the point. When using annotations which rely on an entity, it's > warmly recommended (and even mandatory) to have a parameter in the annotated > java method. > > Best regards, > Thierry Boileau > > ------------------------------------------------------ > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2656741 > -- Fabián Mandelbaum IS Engineer ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2667825
