Ahh great, I see the possibility now. I know 'deep' PROPFINDs (even ones requested with a Vector or props) return Enumeration objects... but do these contain the doc URI? In the early stages I patch the URI in as a document property, as its not always readily retrievable (at least not in a store independent manner) so I could simply add the URI property to the Vector of props to be PROPFIND'd.
I am having other difficulties now though... my custom webdavservlet is stepping-in and trying to handle the POST request that my file upload JSP page is trying to make to my UploadFileHandler servlet... If there was a way to get the webdav servlet to route the request according to the URL of the JSP page it came from (or some other identifier), then that would be perfect. getRequestURL() doesn't seem to work, as it seems to just return the URL that the uploaded file would have if the upload succeeded NOT the JSP page the upload is sent from... getRequestDispatcher() seems to not be quite what I am looking for... of course I am probably wrong. Many thanks Regards stu -----Original Message----- From: Ingo Brunberg [mailto:[EMAIL PROTECTED] Sent: 04 September 2003 16:42 To: [EMAIL PROTECTED] Subject: Re: Search facility - document iterator Maybe I was not clear enough, but I aleady mentioned that you can do a PROPFIND with depth infinity on every resource (including the root resource) in your store. This will give you the requested properties of all resources rooted under that resource. Depending on the size of your store this is of course a big attack on your server. For this reason a server may limit the maximal depth to some other value than infinity. Maybe this is a configurable parameter in Slide (I am not quite sure). If you want to handle every document through iteration just search the net for tree traversal algorithms. Regards, Ingo > That is a shame. I just don't have time to set up slide 2. =20 > > Any ideas on how I can PROPFIND all documents in the store easily, in a > loop? That's all I need. > > Many thanks > > Stuart --------------------------------------------------------------------- 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]
