Michael Smith wrote:

"propget resourcename" in cadaver actually issues an allprop request, which was originally designed to return all the properties on a resource. Later specs (I think this was added in the DeltaV spec?) realised that this was a bad idea (because some properties are expensive to compute), so allow some properties to not get returned by allprop. DAV:group-member-set is one such.

So, you need to request the property specifically with cadaver. Since it's in a non-default namespace (i.e. not in _cadaver_'s default namespace, which seems to be http://webdav.org/cadaver/custom-properties/ ), you need to change that first. The following two commands should do what you want:
set namespace "DAV:"
propget resourcename group-member-set

thanks for the tip, that worked perfectly.

after writing more tests, i found something else interesting (again, this is with the slide client lib):

1) when i do a propfind for /roles/ with depth 1, for each of the child resources i get back what i assume are the properties specified by allprop (9 of them, all DAV:).

2) when i do a propfind for /roles/root with depth 0, i get back 10 properties - the same ones above, plus group-member-set.

i haven't figured out if this is a feature of the client api (which is either undocumented, or assumed to be understood by somebody more familiar with webdav than i, or that i simply missed), or if something wacky is going on.

in any event, assuming i want my webapp to present a list of roles, each with their member users, then i guess i'll have to iterate through each of the resources within /roles/ and do a depth 0 propfind. unless i can find some better way to do it with the client api.

thanks again!

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to