Hello, The only way to receive what you want is with:
<request xmlns="http://hippo.nl/webdav/1.0"; xmlns:d="DAV:" xmlns:jx="http://apache.org/cocoon/templates/jx/1.0"; target="${cocoon.parameters.target}" method="PROPFIND"> <header name="Depth" value="Infinity"/> <body> <d:propfind> <d:prop><d:lockdiscovery/></d:prop> </d:propfind> </body> </request> but this obviously returns all documents. You cannot query for locks through a DASL, because (AFAIU but do not know exactly) a lock is a derived property, which might not be something store on the document itself. Just like you cannot DASL on <d:supported-privilege-set/>. They are derived properties, which might be a result of some of its parents. If for example I iterate over all properties of a document with NodeRevisionDescriptor descriptor for(Enumeration e = descriptor.enumerateProperties(); e.hasMoreElements();) { I won't get lockdiscovery or supported-privilege-set. Also setting a lock on a document does not even trigger a save, let alone indexing a lock > > According to the WebDAV spec, this should return a > multistatus response with the description of the lock [1]. The WebDAV spec is regarding method="PROPFIND" and not regarding the method="SEARCH" > > So, my questions: > > * is this a bug in my query or in slide or ... ? > * has any hippo found a better way of querying the repo for > all locked documents? AFAICS, it is not a bug, and no....I haven't tried it before but I would not be able to come up with a better way I am afraid. -Ard > > http://asg.andrew.cmu.edu/rfc/rfc2518.html#sec-13.8.1 > > Thanks, > > Andrew. > -- > Sourcesense: Making sense of Open Source > Tel: +44 (0)870 741 6658 Fax: +44 (0)700 598 1135 > Web: http://www.sourcesense.com/ > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist
