Thorsten Scherler wrote:
Hi all,when working with a flat directory hierarchy the "lucene.index" usecase does not work anymore. Well I thought that this should not matter for me since ATM I do not need search. ...but I was dead wrong! For example src/webapp/lenya/config/cocoon-xconf/usecases/site/usecase-site-cut.xconf is refering to the above mentioned usecase: ... <exit usecase="lucene.index"> <parameter name="indexAction" value="delete"/> <parameter name="indexArea" value="authoring"/> <parameter name="lenya.exitUsecase" value="tab.overview"/> </exit> ... I can understand that triggering the indexing usecase when moving/deleting/creating/... documents makes sense but I strongly disagree to create such dependencies via exitUsecase in the usecase config files.
+1000
We should remove all such declarations in our usecases and have a central document listener that will handle all events around the documents.
That's a very good idea. Maybe you'd like to make a more detailed proposal?
This way we do not have to use this verbose "dependency magic" which needs a high level of understanding usecases and is hidding the "real" problem (in my case that actually lucene is failing). wdyt?
In any case, these dependencies should be removed, and if this isn't possible, they have to be declared and checked. The listener concept seems to be a useful approach for decoupling indexing from specific usecases. -- Andreas -- Andreas Hartmann Wyona Inc. - Open Source Content Management - Apache Lenya http://www.wyona.com http://lenya.apache.org [EMAIL PROTECTED] [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
