From: Chris T. <chr...@gm...> - 2010-11-14 19:13:51
|
Dear Dmitriy, What I'm reporting then is that what I understand you to describe isn't working. I've put some simple LOG.debug's into the code and the DocumentTrigger is being returned as null at: > //prepare the trigger > DocumentTrigger trigger = doc.getCollection().getDocumentTrigger(context.getBroker()); (I've verified that triggersEnabled == true) when requested on a Document located at: /db/dharmacloud/texts/tbrc/002/001/002-001-001.xml With the following collection.xconf stored at: /db/system/config/db/dharmacloud/texts > <collection xmlns="http://exist-db.org/collection-config/1.0"> > <index> > <!-- Range indexes --> > <create qname="@RID" type="xs:string"/> > <create qname="@restriction" type="xs:string"/> > <create qname="@lang" type="xs:string"/> > <create qname="@organization" type="xs:string"/> > <create qname="@collection" type="xs:string"/> > <create qname="@volume" type="xs:integer"/> > <create qname="@index" type="xs:integer"/> > <create qname="@start" type="xs:integer"/> > <create qname="@end" type="xs:integer"/> > <create qname="@work" type="xs:string"/> > <create qname="@node" type="xs:string"/> > <create qname="@group" type="xs:string"/> > <create qname="@rid" type="xs:string"/> > <create qname="@tag" type="xs:string"/> > <create qname="@folio" type="xs:string"/> > <create qname="@side" type="xs:string"/> > <create qname="@ref" type="xs:string"/> > > <!-- Lucene indexes --> > <lucene> > <analyzer class="info.dharmacloud.database.lucene.TibWhitespaceAnalyzer"/> > <analyzer id="std" class="org.apache.lucene.analysis.standard.StandardAnalyzer"/> > <analyzer id="ws" class="org.apache.lucene.analysis.WhitespaceAnalyzer"/> > <text qname="text"/> > <text qname="info"/> > <text qname="title"/> > <text qname="author"/> > <text qname="provenance" analyzer="std"/> > <text qname="pageset"/> > <text qname="page"/> > <text qname="small"/> > <text qname="acip" analyzer="ws"/> > </lucene> > </index> > <triggers> > <trigger event="store,remove,update" class="org.exist.versioning.VersioningTrigger"> > <parameter name="overwrite" value="no"/> > </trigger> > </triggers> > </collection> Thanks, Chris On Nov 14, 2010, at 12:50 PM, Dmitriy Shabanov wrote: > On Sun, 2010-11-14 at 12:40 -0600, Chris Tomlinson wrote: >> On Nov 14, 2010, at 12:26 PM, Dmitriy Shabanov wrote: >>> On Sun, 2010-11-14 at 12:12 -0600, Chris Tomlinson wrote: >>>> I've tracked down the situation to apparently a disconnect between the >>>> current collection.xconf and apparently some pending changes to put >>>> trigger configuration for a collection separately. When trace the >>>> execution all works as expected except that >>>> Collection.getDocumentTrigger is not returning returning a >>>> DocumentTrigger with no change in the collection.xconf. Is the change >>>> in separating the indexing from the trigger configuration done? I >>> >>> There was the commit >>> http://exist.svn.sourceforge.net/exist/?rev=13087&view=rev >>> >>> It do split index & trigger search. >> >> I saw the comment earlier but I didn't understand it. I do see in the code that there is effort to search up the collection hierarchy but it isn't clear to me whether the trigger configuration is still in the collection.xconf or not. Does "For now, there is only 'override' option." mean that the configuration somehow has to be directly on the collection containing a given document? If so then that won't work since the collection subtree is wide and 4 layers deep - new collection subtrees are being added daily. > > 'override' have the meaning: if you have trigger configurations on /db > & /db/test and do something on /db/test/any-sub-col the trigger > from /db/test will be used, but for /db/any-other trigger from /db. > > 'add': to fire /db & /db/test for /db/test/any-sub-col. > >> >> I guess it would help to have a few words about how the configuration is intended to be. > > It should work with all configurations with out any changers. New one > ignore 'event' attribute. > >> >> >>> >>>> thought not and that the "old" configuration was supposed to still >>>> work? Are triggers in the trunk working for anyone else? As I have >>>> mentioned I don't see any tests running when I do: >>>> >>>> >>>> ./build.sh test >>> >>> There are some tests for versioning >>> http://exist.svn.sourceforge.net/viewvc/exist/trunk/eXist/extensions/versioning/test/ , but I'm not sure that it will be run by ./build.sh test. Do any one know how to run it? >>> >>> Chris, do you have lib/extensions/exist-versioning.jar? >> >> Yes exist-versioning.jar is being properly generated. >> >> Thanks, >> Chris >> >> >> >> >>> >>> -- >>> Cheers, >>> >>> Dmitriy Shabanov >> > -- > Cheers, > > Dmitriy Shabanov |