From: Chris T. <chr...@gm...> - 2010-11-04 08:08:34
|
Dmitriy, I'll give the current trunk a try as soon as I clear some other issues. Where does the configuration get done now - you indicated that it is (or soon will be) not in the collection.xconf. Regards, Chris On Nov 4, 2010, at 10:20 AM, Dmitriy Shabanov wrote: > On Thu, Nov 4, 2010 at 5:45 AM, Chris Tomlinson <chr...@gm...> wrote: > We have been using VersioningTrigger and so will be interested in helping to test whatever changes are involved in the new design. > > I'm very :-) TheVersioningTrigger should work with out any changers, well just configured different way, the old configuration did have event attribute > > <exist:trigger event='store,remove' class='org.exist.collections.triggers.TestTrigger'/> > > new one do not require it, so configuration should be > > <exist:trigger class='org.exist.collections.triggers.TestTrigger'/> > > > I've looked through the various emails and wiki and so forth and I can not find a description or proposal for this significant revamp of triggers and their configuration. > > Can you please point me to such discussion so I can get up-to-speed on what the design goals are and what to expect? > > The only public discussion I can point is http://demo.exist-db.org/exist/irclog/irclog.xql date 2010-11-01. I do plan to document it with examples. > > -- > Dmitriy Shabanov |