|
43 | 43 | <section> |
44 | 44 | <title>XQuery Triggers</title> |
45 | 45 | <para>Triggers written in XQuery may be configured by using the org.exist.collections.triggers. XQueryTrigger to fire the XQuery. |
46 | | - The XQuery to be executed when the trigger is fired may either be placed in the collection.xconf itself or indicated by a URL.</para> |
| 46 | + The XQuery to be executed when the trigger is fired may either be placed in the collectionconfiguration file and store it in the system collection itself or indicated by a URL.</para> |
47 | 47 | <para>The XQuery functions mapped to trigger event:</para> |
48 | 48 | <itemizedlist> |
49 | 49 | <listitem> |
|
162 | 162 | parent). It is furthermore possible for each collection in the hierarchy to have its |
163 | 163 | own <emphasis>trigger creation policy</emphasis> defined by a configuration file.</para> |
164 | 164 | <para>To configure triggers for a given collection - for example: |
165 | | - <filename>/db/foo</filename> - create a new <filename>.xconf</filename> |
166 | | - configuration file and store it in the system collection (e.g. |
167 | | - <filename>/db/system/config/db/foo/collection.xconf</filename>). You may choose any name for this |
168 | | - document so long as it has the <filename>.xconf</filename> extension, although |
169 | | - <filename>collection.xconf</filename> is recommended. Note that |
| 165 | + <filename>/db/foo</filename> - create a new collection configuration file and store it in the system collection (i.e.: |
| 166 | + <filename>/db/system/config/db/foo/collection.xconf</filename>). Note that |
170 | 167 | since subcollections will inherit the configuration policy of their parent |
171 | 168 | collections, you are not required to specify a configuration for every collection.</para> |
172 | | - <note> |
173 | | - <para>You can store only ONE <filename>.xconf</filename> configuration document per |
174 | | - collection in the system collection <filename>/db/system/config</filename>. For |
175 | | - example, the collection <filename>/db/system/config/foo</filename> would contain |
176 | | - one configuration file and/or other subcollections.</para> |
177 | | - </note> |
178 | 169 | <section> |
179 | 170 | <title>Configuration Structure and Syntax</title> |
180 | 171 | <para>Trigger configuration files are standard XML documents that have their elements |
|
0 commit comments