> Hi Ingo,
> I wrote about the PROPPATCH problem on 05/07/2004 in the dev mailing
> list (subject "Client library PROPPATCH on multiple properties"), but
> this message remained unanswered. Do you know if there is something new
> on this?
>
> Also, on the client library, if I issue a PROPFIND
Hi Ingo,
I wrote about the PROPPATCH problem on 05/07/2004 in the dev mailing
list (subject "Client library PROPPATCH on multiple properties"), but
this message remained unanswered. Do you know if there is something new
on this?
Also, on the client library, if I issue a PROPFIND with 10 proper
Np :)
___
Thank you very much for the info Miguel, now i
understand :) the situation there.
--- Miguel Figueiredo <[EMAIL PROTECTED]> wrote:
>
>
> You're almost completly correct, but the "member's
> ancestor's" does not mean
> all descendant members ;)
>
> For example take a collection li
Thank you very much for the info Miguel, now i
understand :) the situation there.
--- Miguel Figueiredo <[EMAIL PROTECTED]> wrote:
>
>
> You're almost completly correct, but the "member's
> ancestor's" does not mean
> all descendant members ;)
>
> For example take a collection like this one
You're almost completly correct, but the "member's ancestor's" does not mean
all descendant members ;)
For example take a collection like this one:
- ole
+ toro
- chica
- Buena.txt
- Gostosa.txt
You intend to delete the 'ole' collection but, the ole/chica/Gostosa.txt
fil
Hello all,
thank you guys for your answers. I think i understand
your reasoning, however i would refer again to the
rfc2518 section 8.6.2 where it states "If any resource
identified by a member URI cannot be deleted then all
of the member's ancestors MUST
NOT be deleted, so as to maintain namespa
This is the same problem as with a PROPPATCH with multiple
properties. The methods in WebdavResource simplify things too much in
returning only a boolean value for these methods that can be partially
successful. Returning false would not be the right thing either.
If you have a good idea how to ta
Hello LZ,
Actually the 207 (multistatus) message is a container for other status
messages. This means that while your request may partially fail, it can also
partially succeed. The multistatus shall return an aggregation of status
messages to the corresponding failure or success.
In your case
Hi,
can somebody please, clarify the following issue with
the WebdavResource.deleteMethod(String) in the client
library?
If i want to delete a collection wich is not empty,
according to the rfc2518 section 8.6.2 "If an error
occurs with a resource other than the resource
identified in the Reques
