Hi, great work. After reading it several times I understand most of it :-) As I'm working on events at the moment I think they could be used to trigger indexing for lucene based search. They provide synchronous event collections (before commit and vetoable) as well as asynchronous event collections (fired after commit). The collection can be filtered, so that only the desired changes are indexed (e.g. create and remove of the same resource within a single transaction can be ignored). To enable content type specific indexing it might be a good way to register some content type specific event listeners that extract the metadata from the resource and generates appropriate properties before storing the revision descriptors so the underlying store. regards, Daniel
Am Dienstag, 3. Februar 2004 15:25 schrieb Wallmer, Martin: > Hi, > > I just checked in a proposal for integrate indexing and search, > jakarta-slide/proposals/indexing (as openOffice and pdf). Christophe, Nick, > would that architecture allow you to integrate your implementation? > Stefano, do you think that defining an indexer outside the store definition > (as stated in chapter Outlook) would meet your requirements? > > Comments welcome, > > regards, > Martin > > __________________________ > Martin Wallmer > Research & Development > Software AG ++49 6151 92 1831 > Uhlandstr. 12 > D 64297 Darmstadt > > > --------------------------------------------------------------------- > 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]
