svn commit: r922625 - in /websites/production/camel/content: cache/main.pageCache schematron.html

[bu...@apache.org]

Author: buildbot
Date: Wed Sep 17 23:17:55 2014
New Revision: 922625

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/schematron.html

Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/camel/content/schematron.html
==============================================================================
--- websites/production/camel/content/schematron.html (original)
+++ websites/production/camel/content/schematron.html Wed Sep 17 23:17:55 2014
@@ -109,7 +109,7 @@
       </otherwise>
    </choice>
 &lt;/route&gt;]]></script>
-</div></div><h3 id="Schematron-Schematronrulesfilelocationgoodpractice">Schematron rules file location good practice</h3><p>Schematron rules can change with business requirement, as such it is recommended to store these rules somewhere in file system. When the schematron component endpoint is started, the rules are compiled into XSLT as a &#160;Java Template Object. This is done only once to minimise the overhead of instantiating Java Template object which can be an expensive operation for large set of rules and given that the process goes through four pipelines of&#160;<a shape="rect" class="external-link" href="http://www.schematron.com/implementation.html" rel="nofollow">XSLT transformations</a></p><h3 id="Schematron-Brieftutorialofschematron">Brief tutorial of schematron</h3><p>Here is an example of schematron rules</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>schematron rules</b></div><div
  class="codeContent panelContent pdl">
+</div></div><h3 id="Schematron-Schematronrulesfilelocation.">Schematron rules file location.</h3><p>Schematron rules can change with business requirement, as such it is recommended to store these rules somewhere in file system. When the schematron component endpoint is started, the rules are compiled into XSLT as a &#160;Java Templates Object. This is done only once to minimise the overhead of instantiating Java Templates object, which can be an expensive operation for large set of rules and given that the process goes through four pipelines of&#160;<a shape="rect" class="external-link" href="http://www.schematron.com/implementation.html" rel="nofollow">XSLT transformations</a>. So if you happen to store the rules in the file system, in the event of an update, all you need is to restart the route or the component. No harm in storing these rules in the class path though, but you will have to build and deploy the component to pick up the changes.</p><h3 id="Schematron-Brieftutorialofs
 chematron">Brief tutorial of schematron</h3><p>Here is an example of schematron rules</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>schematron rules</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
 &lt;schema xmlns=&quot;http://purl.oclc.org/dsdl/schematron&quot;&gt;
    &lt;title&gt;Check Sections 12/07&lt;/title&gt;