yes i am, but please be patient.WebDAV support: I'd like to see if the guy who came up with xincon might be interested in joining efforts and maybe donate his code
This is great news :-)
I will make a rewrite to communicate with other apis and to integrate
the application easily in the xindice server.
What do you mean exactly with "communicate with other apis"?
OK, slide is a complete content management system, look at it, it is overkill if you want to integrate it into xindice!
Definitely. Yet it's there, it's a Jakarta project and it has a nice community around. But I decided too not to go the Slide way, at least for now.
the tomcat impl use JNDI, i don't know, but if you write a xindice JNDI impl. you can use it.
Not to mention that a JNDI provider for Xindice might turn out as very useful stuff for lots of things, J2EE being the first that comes to my mind.
But there are problems with both impl: if you change something not through the webdav interface (for example del a resource with the xmldb api) you will get ghosts in slide
I don't really understand the reason for this (note, I don't know Slide that much). Care to share some words on this topic?
OK, solution: take the tomcat impl. and delete the locking stuff. The problem is, that you have to rewrite 95% of the complete servlet, that is xincon!
I had a (unfortunately quick) look at your code and I undertand perfectly what you are saying. :-) Basically I was following the same approach but I was scared by a class that could well end up to thousands of lines (yours is 1326...) so I was designing it as a set of classes (one per method) and a servlet frontend. Also, I was planning to use XSLT for XML responses, which seems to me the most flexible way (also would take the catalina dependency out). Finally, log4j... well, AFAIK there is a general consensus on using Avalon, so I'd suggest to use LogKit.
In short: I'd like to work on this with you (given also that I see you are planning a rewrite). What about it?
Ciao,
-- Gianugo Rabellino
