Hello,

I'm currently working on extending the lucene auditor and I was womdering if there were some ideas on the way it should be done.

I'm about to do it this way :
- take example of the file auditor to persist the exchanges but I would like to persist the payload and the header information separately each going in it's own file. - persist header information in XML form to simplify further indexing. As Lucene allows keywords definition it will be possible to pass a map of keywords and xpath expressions that would be grabbed from the payload. It must be possible to define keywords from the header of the message (but I don't know which ones are interresting) - when an exchange is sent I plan to do the indexing stuff, maybe in it's own thread even if I don't know at this stage if it is the good way to do so (I guess there's a clean way to start a service) I read that opening and closing the index has a strong impact on performance but I would like the exchange to show up immediately.
- at the restart of servicemix the index would be rebuilt

Do you have any comments further ideas or suggestions on this ?

Benoît

Reply via email to