The reportMethod(URL, properties, depth) gets the correct XML response back, however the enumeration class that is returned only has strings in it and shows up blank for the label-name-set prop. I'm not sure if the bug is in the method or in the underlying ReportMethod class at this point, but I'm sure it is a bug. I'm implementing a workaround by subclassing WebdavResouce. Perhaps I could submit that after I get it to work properly?
----- Original Message ----- From: "Michael Smith" <[EMAIL PROTECTED]> To: "Slide Users Mailing List" <[EMAIL PROTECTED]> Sent: Wednesday, June 16, 2004 9:00 PM Subject: Re: How can I determine what version has a given label > Ingo Brunberg wrote: > >>kranga wrote: > >> > >>>I've tried using propfind <path> label-name-set and this returns blank. The > >>>label property holds a set of labels as a revision can have multiple labels. > >>>How do I query the labels out? Someone please help! > >> > >>You need to do your propfind (for label-name-set) on the version paths. > >>There's no simple/quick way to say 'give me a list of all the labels > >>that are set on any version of this resource' (an argument could > >>certainly be made that this would be a useful thing, though) as far as I > >>know. > > > > > > No, there is a way of doing this. Just use the REPORT method on your > > version controlled resource and ask for the label-name-set. > > Ah. My mistake - I was using the RFC as my reference (since I have a > helpful printed out copy sitting next to me). The relevant REPORT (and > the deprecation of the Label header) was added in the errata, which I > hadn't read. > > > > > > >>Fetching a particular version with a label set is, of course, much > >>simpler - just set the Label header appropriately. > >> > >>Mike > > > > > > The Label header is deprecated. I'm not sure if it is supported by > > Slide anyway. You have to find out (from the results of the REPORT > > method) which version has a given label set. Then you request exactly > > that version by a simple GET. > > Label header is supported by slide - it's quite useful. The REPORT > approach is sensible too, of course, but I haven't checked if slide > supports it. > > Mike > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
