On Sun, 2004-01-18 at 04:34, Nick Reddel wrote: > Hi everyone > > I have developed an indexing store (subclassing j2ee/rdbms > adapter)(which indexes properties, NOT content), at the moment just for > MySQL 4.1+ but presumably easily transferable to any othe RDMS that > supports subselects. But...the code is horrible and undocumented, > because as soon as I got it working I then moved on to a "virtual" store > (i.e. a relational filesystem, which will be the sweetest thing as soon > as I've sorted out some sort of leak which means the connections don't > go back to the pool). > > The reason I did some of the strange things I did, which I've marked > below with (!), is that I've made a refreshing Netbeans webdav client, > which for the sake of completeness needs to know if absolutely any > modifications have happened to a given uri/object/file, particularly > lock changes. My idea was to have a group of authors working on the same > set of files, only allowing offline content changes if the file's > checked out, rather than the local/remote model that's standard. I'll > explain why if anyone's interested, but in another mail. > > So> a few notes/queries on the implementation. I can upload my sources, > but I'd need a little time to make it slightly less embarassing, and any > input/critiques I can get on the solution below (architecturally I find > Slide a completely impossible act to follow. Which makes me a little > shy). > > My last update from CVS was early December, and I modified some > org.apache.slide files as needed - I'd imagine similar modifications > would be needed for any indexing implementation: > > Search languages: > ----------------- > > There is API support for different search languages, but no actual > implementation. > > In Domain.xml, I added a new parameter for search languages and patched > SearchImpl.java as per attachment > > <parameter > name="search_language_classes">org.apache.slide.search.basic.BasicSearch > Language, > > com.ella.alexis.chakriya.slide.indexing.MultipleSearchLanguage</paramete > r> > > </configuration> > > Property indexing > ----------------- > > Two separate issues - creation of the indexing table (s), and index > updating > > Index table creation/rebuilding. > > - the better way to do this would be through Slide Admin. But > > 1. is slide admin maintained? (no). do you want someone to maintain it? > 2. is there any way in Tomcat/servlet containers to define webapp > dependencies, and hence classloader access across webapps, rather than > "copy it all into common", which sort of defeats the purpose of webapps?
Excellent point, and I am taking a different approach to Admin that seems to work out well. I have created my own "Admin" Struts Application, by taking the approach that Admin is a "Client" to Slide. My Admin Actions then "Connect" to Slide through the webdavresource like any client. This allows me to Browse the Slide Folders, look at Properties, Lock, Unlock, View ACLs and Add/Edit ACLs all through Struts Actions and avoid the "copy it all into common" as well as allows the Admin WebApp to be located anywhere, not just on one instance. Ollie
