Re: Re: Re: Re: PROPFIND doesn't work anymore after the switch from 2.0RC4 to 2.0.0

2010-10-04 Thread Fabian Mandelbaum
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

RE: Re: Re: Re: PROPFIND doesn't work anymore after the switch from 2.0RC4 to 2.0.0

2010-10-04 Thread Jerome Louvel
: Re: Re: Re: Re: PROPFIND doesn't work anymore after the switch from 2.0RC4 to 2.0.0 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

RE: Re: Re: Re: PROPFIND doesn't work anymore after the switch from 2.0RC4 to 2.0.0

2010-09-08 Thread Thierry Boileau
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

Re: Re: Re: Re: PROPFIND doesn't work anymore after the switch from 2.0RC4 to 2.0.0

2010-09-08 Thread Fabian Mandelbaum
Hello Thierry, Thanks for your answers. Is there a simple way on Restlet's side to enforce us, lazy developers, to pass such params (actually a Representation class) on annotated method handlers? What happens if I use the signature you propose with DomRepresentation as the entity parameter to

RE: Re: Re: PROPFIND doesn't work anymore after the switch from 2.0RC4 to 2.0.0

2010-09-01 Thread Thierry Boileau
Hello Fabian, I feel very sorry for answering so late... Can you try with this signature? public Representation propfind(Representation rep) throws ResourceException { [...] final DomRepresentation reqXML = new DomRepresentation(rep); [...] } Best regards, Thierry Boileau

Re: Re: Re: PROPFIND doesn't work anymore after the switch from 2.0RC4 to 2.0.0

2010-09-01 Thread Fabian Mandelbaum
Bonsoir Thierry, no problem for answering late, I know it's holidays time over there (hope you enjoyed yours, if any). I tried with the proposed change and PROPFIND is properly handled now, it works. I've also added a debug log output like this (I had to use reqRep instead of rep as the param

Re: Re: PROPFIND doesn't work anymore after the switch from 2.0RC4 to 2.0.0

2010-08-04 Thread Fabian Mandelbaum
Hello Thierry, I've made two tests, one with the following signature: @Propfind public Representation propfind(Variant variant) throws ResourceException It behaved like the original version, that is HTTP 405 (Method Not Allowed). The following test was with the signature you proposed, and now

RE: Re: PROPFIND doesn't work anymore after the switch from 2.0RC4 to 2.0.0

2010-08-03 Thread Thierry Boileau
Hello Fabian, I guess the converter service is messing a little bit here. Can you try with the following signature? @Propfind public Representation propfind(String text) throws ResourceException I have a look at your code. Best regards, Thierry Boileau