lucene index configuration

On Fri, 2006-03-24 at 16:38 +0100, Andreas Hartmann wrote:
> Josias Thöny wrote:
[...] 
> > There are still open issues about lucene search,
e.g. it still uses the
> > exit-usecase to trigger indexing. 
> 
> JCR provides an observation mechanism, I guess we need
something
> similar for documents (e.g., to trigger the indexing).

+1
Do you have an idea how the triggering could work?

Maybe changing the content of documents should happen behind
the Lenya
API, something like

document.save(inputStream)
 or
documentManager.saveDocument(document, inputStream)

(it would read the inputstream and write it into the
document)

then the document or the documentManager could notify any
"document
change listeners".
Or would that be the job of each individual code block which
changes
documents, like e.g. OneFormEditor.java?

WDYT?

Josias

> 
> -- Andreas
> 


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org

Josias Thöny wrote:
> On Fri, 2006-03-24 at 16:38 +0100, Andreas Hartmann
wrote:
>> Josias Thöny wrote:
> [...] 
>>> There are still open issues about lucene
search, e.g. it still uses the
>>> exit-usecase to trigger indexing. 
>> JCR provides an observation mechanism, I guess we
need something
>> similar for documents (e.g., to trigger the
indexing).
> 
> +1
> Do you have an idea how the triggering could work?
> 
> Maybe changing the content of documents should happen
behind the Lenya
> API,

+1

 > something like
> 
> document.save(inputStream)
>  or
> documentManager.saveDocument(document, inputStream)

The new repository API draft provides a method

   Translation.getOutputStream()


The notification could take place in the stream's close()
method:

   class DocumentOutputStream extends ByteArrayOutputStream
{

         public void close() throws IOException {
             ...
             notifyListeners();
         }
   }


> (it would read the inputstream and write it into the
document)
> 
> then the document or the documentManager could notify
any "document
> change listeners".
> Or would that be the job of each individual code block
which changes
> documents, like e.g. OneFormEditor.java?

No, I don't think that would be a good idea.

-- Andreas



-- 
Andreas Hartmann
Wyona Inc.  -   Open Source Content Management   -   Apache
Lenya
http://www.wyona.com     
                http://lenya.apache.org
andreas.hartmannwyona.com                     andreasapache.org


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org