Hi,For me, it is ok. In fact, I stopped my implementation in order to be sure to follow the same ideas. So, that's good for me to rewrite some part.
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?
If I understand, new code is needed for :
* For the search service :
* JDBC implementation for the search service. Anyway we can still used the current generic implementation.
* Give more flexibility in the search service in order to support all scenarios mentionned in your proposal.
* An indexer for content and/or properties. I have one in my proposal based on the existing interface "org.apache.slide.store.IndexStore". I can make some clean-up. After a lucene implementation can be started.
* Modify the ParentStore in order to call the indexer. My proposal used an index helper but you are right, it is better to do it in a Store like ParentStore.
Is it correct ? Martin, do you plan to start this new stuff in short term ? Do you need some help ?
Last point, what about the properties to display for a search result. Sometime, it should be interesting to have a simple list of content references with only a subset of the document proporties.
So, the search service can also optimize the way of building the properties to used (eg. for a JDBC implementation, the select part of a sql statment).
Christophe
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
