Andreas Hartmann wrote:
Robert Goene wrote:
I want to use the LuceneIndexTransformer to update the lucene index
when a page is published. This transformer does provide exactly the
functions i need for 'incremental' and 'configurable' indexing possible.
Maybe it is possible to use this transformer from the usecase handler
itself, is it?
This would be a quite bad design. Generally, a transformer should not
be used for this purpose. Rather extract the index update functionality
in a separate service which you access from the usecase handler.
The transformer does exactly the job it requires to do. It makes the
configurable indexing of pages a very easy job. With the use of a xslt
sheet, one can select the fields that must be indexed.
Bad design would also be reimplementing an already existing and
established piece of code, especially when it meets the requirements of
my project (lenya-search SoC).
I do agree that calling a usecase from the usecase handler is not
pretty. As adding an index step to the workflow is not a very
attractive, i am looking for a way to embed the usecase in the current
publication process. Can you give me some advice on this issue?
Regards, Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
