Ciao, in these days I wanted to test Eclipse (BTW, looks really great! too bad it does a bad job with indenting...) and I found the time to come up with an XPath-enabled DirectoryGenerator wich uses the X-pointerish syntax already implemented in the XMLDB stuff.
I find it really useful for my needs: the capability of having XPath queries in directory listings allows to get basic metadata from the XML documents that can be used for a number of things: as an example this might allow us to forget about book.xml for the Cocoon docs since the needed metadata would be pulled out from the files themselves. Now, before committing it, I have some questions: 1. XPathProcessor has been migrated to Avalon (release, not scratchpad) and AFAIK the Avalon version is the only one that will be maintained in the future, so I have used org.apache.avalon.excalibur.xml.xpath.XPathProcessor in my code; cocoon.roles, however, still points to the Cocoon implementation so, if committed, my code would not work unless we change cocoon.roles too. I think that this shouldn't bring any problem. The same goes for the parser abstraction (though I've used the Cocoon one since this component is still in Avalon's scratchpad): Carsten's last email was definitely appropriate :) What's the best thing to do? Of course I can change my code and switch to Cocoon's XPathProcessor, but I don't like this solution that much. 2. Scratchpad or not? I'd go for the first, see if it works and behaves and then move it to the stable tree with some docs. 3. It might be the case to add this feature not as another generator but as an option to DirectoryGenerator itself (and, why not to FileGenerator as well). Maybe it's only me finding this stuff really useful, but I have the feeling that it might save lots of butts in real life. With this I can have a poor man's CMS with WEBDAV support built in minutes :) Ciao, -- Gianugo Rabellino --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
