Re: [Exist-development] VersionTrigger configuration changed?

[Chris T. <chr...@gm...>]

Hello,

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 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

Thanks,
Chris



On Nov 12, 2010, at 6:28 PM, Chris Tomlinson wrote:

> Hello,
> 
> It appears that the VersioningTrigger is not firing any longer in trunk - it was back on rev 12826.
> 
> I've updated to rev 13200 and ran:
> 
> ./build.sh rebuild
> ./build.sh test
> 
> I didn't see any testing of Versioning. I don't see a "test" target in extensions/versioning/build.xml so I guess I don't understand how versioning testing is supposed to be fired. In the test application I don't see VersionTrigger firing. I was looking to examine an issue that I had earlier with versioning and now am puzzled as to whether the configuration of versioning has been changed or whether something else has happened. I understand that there's been some change in the versioning flow.
> 
> The configuration that I've been using was firing in rev 12826:
> 
>> <collection xmlns="http://exist-db.org/collection-config/1.0">
>>     <index>        
>  .. .. ..
>>     </index>
>>     <triggers>
>>         <trigger event="store,remove,update" class="org.exist.versioning.VersioningTrigger">
>>             <parameter name="overwrite" value="no"/>
>>         </trigger>
>>     </triggers>
>> </collection>
> 
> 
> and now does not appear to fire.
> 
> From prior commits it appears that this should still be working.
> 
> Am I failing to setup some configuration?
> 
> Thanks,
> Chris
>