camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r979924 [1/2] - in /websites/production/camel/content: book-component-appendix.html book-in-one-page.html cache/main.pageCache validation.html xslt.html
Date Tue, 09 Feb 2016 09:21:08 GMT
Author: buildbot
Date: Tue Feb  9 09:21:07 2016
New Revision: 979924

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/book-component-appendix.html
    websites/production/camel/content/book-in-one-page.html
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/validation.html
    websites/production/camel/content/xslt.html

Modified: websites/production/camel/content/book-component-appendix.html
==============================================================================
--- websites/production/camel/content/book-component-appendix.html (original)
+++ websites/production/camel/content/book-component-appendix.html Tue Feb  9 09:21:07 2016
@@ -1016,11 +1016,11 @@ template.send("direct:alias-verify&
 ]]></script>
 </div></div><p></p><h3 id="BookComponentAppendix-SeeAlso.8">See Also</h3>
 <ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul><ul><li><a shape="rect" href="crypto.html">Crypto</a> Crypto is also available as a <a shape="rect" href="data-format.html">Data Format</a></li></ul> <h2 id="BookComponentAppendix-CXFComponent">CXF Component</h2><div class="confluence-information-macro confluence-information-macro-note"><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>When using CXF as a consumer, the <a shape="rect" href="cxf-bean-component.html">CXF Bean Component</a> allows you to factor out how message payloads are received from their processing as a RESTful or SOAP web service. This has the potential of using a multitude of transports to cons
 ume web services. The bean component's configuration is also simpler and provides the fastest method to implement web services using Camel and CXF.</p></div></div><div class="confluence-information-macro confluence-information-macro-tip"><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>When using CXF in streaming modes (see DataFormat option), then also read about <a shape="rect" href="stream-caching.html">Stream caching</a>.</p></div></div><p>The <strong>cxf:</strong> component provides integration with <a shape="rect" href="http://cxf.apache.org">Apache CXF</a> for connecting to JAX-WS services hosted in CXF.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1454973515557 {padding: 0px;}
-div.rbtoc1454973515557 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1454973515557 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1455009470590 {padding: 0px;}
+div.rbtoc1455009470590 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1455009470590 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style></p><div class="toc-macro rbtoc1454973515557">
+/*]]>*/</style></p><div class="toc-macro rbtoc1455009470590">
 <ul class="toc-indentation"><li><a shape="rect" href="#BookComponentAppendix-CXFComponent">CXF Component</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#BookComponentAppendix-URIformat">URI format</a></li><li><a shape="rect" href="#BookComponentAppendix-Options">Options</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#BookComponentAppendix-Thedescriptionsofthedataformats">The descriptions of the dataformats</a>
@@ -10498,7 +10498,7 @@ from(&quot;seda:someEndpoint&quot;).
     &lt;!-- use the same version as your Camel core version --&gt;
 &lt;/dependency&gt;
 ]]></script>
-</div></div><p>From Camel 2.9 onwards the <a shape="rect" href="validation.html">Validation</a> component is provided directly in the camel-core.</p><h3 id="BookComponentAppendix-Options.56">Options</h3><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Option</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">resourceResolverFactory</td><td colspan="1" rowspan="1" class="confluenceTd">DefaultValidatorResourceResolverFactory</td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17</strong>: Reference to a <code>org.apache.camel.component.validator.ValidatorResourceResolverFactory </code>which creates a resource resolver per endpoint<code>. </code><span>The default implementation returns an instance of <code><span>org
 .apache.camel.component.validator.</span>DefaultLSResourceResolver </code></span><span><span>which reads the schema files from the classpath and the file system. This option instead of the option <code>resourceResolver</code> shall be used when the resource resolver depends on the resource URI of the root schema document specified in the endpoint. This option is also available on the validator component, so that you can set the resource resolver factory only once for all endpoints.</span></span></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>resourceResolver</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong> Reference to a <code>org.w3c.dom.ls.LSResourceResolver</code> in the <a shape="rect" href="registry.html">Registry</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useDom</code></p></td><td colspan="1" ro
 wspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Whether <code>DOMSource</code>/<code>DOMResult</code> or <code>SaxSource</code>/<code>SaxResult</code> should be used by the validator.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useSharedSchema</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> Whether the <code>Schema</code> instance should be shared or not. This option is introduced to work around a <a shape="rect" class="external-link" href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6773084" rel="nofollow">JDK 1.6.x bug</a>. Xerces should not have this issue.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>failOnNullBody</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" row
 span="1" class="confluenceTd"><p><strong>Camel 2.9.5/2.10.3:</strong> Whether to fail if no body exists.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>headerName</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.11:</strong> To validate against a header instead of the message body.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>failOnNullHeader</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.11:</strong> Whether to fail if no header exists when validating against a header.</p></td></tr></tbody></table></div></div><h3 id="BookComponentAppendix-Example.11">Example</h3><p>The following <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/camel/trunk/components/camel-spring/src/test/resou
 rces/org/apache/camel/component/validator/camelContext.xml">example</a> shows how to configure a route from endpoint <strong>direct:start</strong> which then goes to one of two endpoints, either <strong>mock:valid</strong> or <strong>mock:invalid</strong> based on whether or not the XML matches the given schema (which is supplied on the classpath).</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>From Camel 2.9 onwards the <a shape="rect" href="validation.html">Validation</a> component is provided directly in the camel-core.</p><h3 id="BookComponentAppendix-Options.56">Options</h3><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Option</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">resourceResolverFactory</td><td colspan="1" rowspan="1" class="confluenceTd">DefaultValidatorResourceResolverFactory</td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17</strong>: Reference to a <code>org.apache.camel.component.validator.ValidatorResourceResolverFactory </code>which creates a resource resolver per endpoint<code>. </code><span>The default implementation creates an instance of <code><span>org
 .apache.camel.component.validator.</span>DefaultLSResourceResolver per endpoint </code></span><span><span>which creates the default resource resolver <code><span>org.apache.camel.component.validator.</span>DefaultLSResourceResolver. The default resource resolver</code> reads the schema files from the classpath and the file system. This option instead of the option <code>resourceResolver</code> shall be used when the resource resolver depends on the resource URI of the root schema document specified in the endpoint; for example, if you want to extend the default resource resolver. This option is also available on the validator component, so that you can set the resource resolver factory only once for all endpoints.</span></span></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>resourceResolver</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong
 > Reference to a <code>org.w3c.dom.ls.LSResourceResolver</code> in the <a shape="rect" href="registry.html">Registry</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useDom</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Whether <code>DOMSource</code>/<code>DOMResult</code> or <code>SaxSource</code>/<code>SaxResult</code> should be used by the validator.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useSharedSchema</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> Whether the <code>Schema</code> instance should be shared or not. This option is introduced to work around a <a shape="rect" class="external-link" href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6773084" rel="nofollow">JDK 1.6.x bug</a>. 
 Xerces should not have this issue.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>failOnNullBody</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9.5/2.10.3:</strong> Whether to fail if no body exists.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>headerName</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.11:</strong> To validate against a header instead of the message body.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>failOnNullHeader</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.11:</strong> Whether to fail if no header exists when validating against a header.</
 p></td></tr></tbody></table></div></div><h3 id="BookComponentAppendix-Example.11">Example</h3><p>The following <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/camel/trunk/components/camel-spring/src/test/resources/org/apache/camel/component/validator/camelContext.xml">example</a> shows how to configure a route from endpoint <strong>direct:start</strong> which then goes to one of two endpoints, either <strong>mock:valid</strong> or <strong>mock:invalid</strong> based on whether or not the XML matches the given schema (which is supplied on the classpath).</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
 &lt;route&gt;
     &lt;from uri=&quot;direct:start&quot;/&gt;
@@ -10770,7 +10770,7 @@ from(&quot;activemq:My.Queue&quot;).
     &lt;!-- use the same version as your Camel core version --&gt;
 &lt;/dependency&gt;
 ]]></script>
-</div></div><p>From Camel 2.9 onwards the <a shape="rect" href="xslt.html">XSLT</a> component is provided directly in the camel-core.</p><h3 id="BookComponentAppendix-Options.60">Options</h3><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default Value</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>converter</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Option to override default <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/converter/jaxp/XmlConverter.html">XmlConverter</a>. Will lookup for the converter in the <a shape="rect" href="registry.html">Re
 gistry</a>. The provided converted must be of type org.apache.camel.converter.jaxp.XmlConverter.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>transformerFactory</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Option to override default <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/transform/TransformerFactory.html" rel="nofollow">TransformerFactory</a>. Will lookup for the transformerFactory in the <a shape="rect" href="registry.html">Registry</a>. The provided transformer factory must be of type javax.xml.transform.TransformerFactory.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>transformerFactoryClass</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Option to override default <a shape=
 "rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/transform/TransformerFactory.html" rel="nofollow">TransformerFactory</a>. Will create a TransformerFactoryClass instance and set it to the converter.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>uriResolver</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.3</strong>: Allows you to use a custom <code>javax.xml.transformation.URIResolver</code>. Camel will by default use its own implementation <code>org.apache.camel.builder.xml.XsltUriResolver</code> which is capable of loading from classpath.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>resultHandlerFactory</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> Allo
 ws you to use a custom <code>org.apache.camel.builder.xml.ResultHandlerFactory</code> which is capable of using custom <code>org.apache.camel.builder.xml.ResultHandler</code> types.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>failOnNullBody</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> Whether or not to throw an exception if the input body is null.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>deleteOutputFile</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.6:</strong> If you have <code>output=file</code> then this option dictates whether or not the output file should be deleted when the <a shape="rect" href="exchange.html">Exchange</a> is done processing. For example suppose the output 
 file is a temporary file, then it can be a good idea to delete it after use.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>output</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>string</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> Option to specify which output type to use. Possible values are: <code>string, bytes, DOM, file</code>. The first three options are all in memory based, where as <code>file</code> is streamed directly to a <code>java.io.File</code>. For <code>file</code> you <strong>must</strong> specify the filename in the IN header with the key <code>Exchange.XSLT_FILE_NAME</code> which is also <code>CamelXsltFileName</code>. Also any paths leading to the filename must be created beforehand, otherwise an exception is thrown at runtime.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>contentCache</code></p></td><td colspan="1" rowspan="1" class
 ="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.6:</strong> Cache for the resource content (the stylesheet file) when it is loaded. If set to <code>false</code> Camel will reload the stylesheet file on each message processing. This is good for development. <br clear="none"> Note: from <strong>Camel 2.9</strong> a cached stylesheet can be forced to reload at runtime via JMX using the <code>clearCachedStylesheet</code> operation.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>allowStAX</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.8.3/2.9:</strong> Whether to allow using StAX as the <code>javax.xml.transform.Source</code>. The option is default <code>false</code> in Camel 2.11.3/2.12.2 or older. And default <code>true</code> in Camel 2.11.4/2.12.3 onwards.</p></td></tr><tr><td colspan="1" ro
 wspan="1" class="confluenceTd"><p><code>transformerCacheSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9.3/2.10.1:</strong> The number of <code>javax.xml.transform.Transformer</code> object that are cached for reuse to avoid calls to <code>Template.newTransformer()</code>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>saxon</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.11:</strong> Whether to use Saxon as the <code>transformerFactoryClass</code>. If enabled then the class <code>net.sf.saxon.TransformerFactoryImpl</code>. You would need to add Saxon to the classpath.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">errorListener</td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" row
 span="1" class="confluenceTd"><strong>Camel 2.14:</strong> Allows to configure to use a custom <code>javax.xml.transform.ErrorListener</code>. Beware when doing this then the default error listener which captures any errors or fatal errors and store information on the Exchange as properties is not in use. So only use this option for special use-cases.</td></tr></tbody></table></div></div><h3 id="BookComponentAppendix-UsingXSLTendpoints">Using XSLT endpoints</h3><p>For example you could use something like</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>From Camel 2.9 onwards the <a shape="rect" href="xslt.html">XSLT</a> component is provided directly in the camel-core.</p><h3 id="BookComponentAppendix-Options.60">Options</h3><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default Value</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>converter</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Option to override default <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/converter/jaxp/XmlConverter.html">XmlConverter</a>. Will lookup for the converter in the <a shape="rect" href="registry.html">Re
 gistry</a>. The provided converted must be of type org.apache.camel.converter.jaxp.XmlConverter.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>transformerFactory</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Option to override default <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/transform/TransformerFactory.html" rel="nofollow">TransformerFactory</a>. Will lookup for the transformerFactory in the <a shape="rect" href="registry.html">Registry</a>. The provided transformer factory must be of type javax.xml.transform.TransformerFactory.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>transformerFactoryClass</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Option to override default <a shape=
 "rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/transform/TransformerFactory.html" rel="nofollow">TransformerFactory</a>. Will create a TransformerFactoryClass instance and set it to the converter.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><code>uriResolverFactory</code></td><td colspan="1" rowspan="1" class="confluenceTd"><code>DefaultXsltUriResolverFactory</code></td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17</strong>: <span style="color: rgb(51,51,51);">&#160;Reference to a&#160;</span><code style="text-align: left;">org.apache.camel.component.</code><code style="text-align: left;">xslt</code><code style="text-align: left;">.</code><span style="color: rgb(51,51,51);"><code>XsltUriResolverFactory</code> which creates an URI resolver per endpoint</span><code style="text-align: left;">.</code><span style="color: rgb(51,51,51);">The default implementation returns an instance of&#160;<code><span>org.
 apache.camel.component.xslt.</span></code></span><span style="color: rgb(51,51,51);"><span><code>DefaultXsltUriResolverFactory</code> which creates the default URI resolver&#160;<span style="color: rgb(51,51,51);"><span><span style="color: rgb(51,51,51);"><code><span>org.apache.camel.builder.</span><span>xml</span></code></span>.XsltUriResolver</span></span> per endpoint. The default URI resolver reads XSLT documents from the classpath and the file system. This option instead of the option <code>uriResolver</code>&#160;shall be used when the URI resolver depends on the resource URI of the root XSLT document specified in the endpoint; for example, if you want to extend the default URI resolver. This option is also available on the XSLT component, so that you can set the resource resolver factory only once for all endpoints.</span></span></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>uriResolver</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><
 p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.3</strong>: Allows you to use a custom <code>javax.xml.transformation.URIResolver</code>. Camel will by default use its own implementation <code>org.apache.camel.builder.xml.XsltUriResolver</code> which is capable of loading from classpath.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>resultHandlerFactory</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> Allows you to use a custom <code>org.apache.camel.builder.xml.ResultHandlerFactory</code> which is capable of using custom <code>org.apache.camel.builder.xml.ResultHandler</code> types.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>failOnNullBody</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspa
 n="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> Whether or not to throw an exception if the input body is null.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>deleteOutputFile</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.6:</strong> If you have <code>output=file</code> then this option dictates whether or not the output file should be deleted when the <a shape="rect" href="exchange.html">Exchange</a> is done processing. For example suppose the output file is a temporary file, then it can be a good idea to delete it after use.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>output</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>string</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> Option to specify which output type to use. Possible 
 values are: <code>string, bytes, DOM, file</code>. The first three options are all in memory based, where as <code>file</code> is streamed directly to a <code>java.io.File</code>. For <code>file</code> you <strong>must</strong> specify the filename in the IN header with the key <code>Exchange.XSLT_FILE_NAME</code> which is also <code>CamelXsltFileName</code>. Also any paths leading to the filename must be created beforehand, otherwise an exception is thrown at runtime.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>contentCache</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.6:</strong> Cache for the resource content (the stylesheet file) when it is loaded. If set to <code>false</code> Camel will reload the stylesheet file on each message processing. This is good for development. <br clear="none"> Note: from <strong>Camel 2.9</strong> a cached 
 stylesheet can be forced to reload at runtime via JMX using the <code>clearCachedStylesheet</code> operation.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>allowStAX</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.8.3/2.9:</strong> Whether to allow using StAX as the <code>javax.xml.transform.Source</code>. The option is default <code>false</code> in Camel 2.11.3/2.12.2 or older. And default <code>true</code> in Camel 2.11.4/2.12.3 onwards.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>transformerCacheSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9.3/2.10.1:</strong> The number of <code>javax.xml.transform.Transformer</code> object that are cached for reuse to avoid calls to <code>Template.newTransformer()</code
 >.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>saxon</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.11:</strong> Whether to use Saxon as the <code>transformerFactoryClass</code>. If enabled then the class <code>net.sf.saxon.TransformerFactoryImpl</code>. You would need to add Saxon to the classpath.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">errorListener</td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.14:</strong> Allows to configure to use a custom <code>javax.xml.transform.ErrorListener</code>. Beware when doing this then the default error listener which captures any errors or fatal errors and store information on the Exchange as properties is not in use. So only use this option for special use-cases.</td></tr></tbody></table></div></
 div><h3 id="BookComponentAppendix-UsingXSLTendpoints">Using XSLT endpoints</h3><p>For example you could use something like</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[from(&quot;activemq:My.Queue&quot;).
   to(&quot;xslt:com/acme/mytransform.xsl&quot;);
 ]]></script>

Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Tue Feb  9 09:21:07 2016
@@ -3731,11 +3731,11 @@ The tutorial has been designed in two pa
 While not actual tutorials you might find working through the source of the various <a shape="rect" href="examples.html">Examples</a> useful.</li></ul>
 
 <h2 id="BookInOnePage-TutorialonSpringRemotingwithJMS">Tutorial on Spring Remoting with JMS</h2><p>&#160;</p><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Thanks</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This tutorial was kindly donated to Apache Camel by Martin Gilday.</p></div></div><h2 id="BookInOnePage-Preface">Preface</h2><p>This tutorial aims to guide the reader through the stages of creating a project which uses Camel to facilitate the routing of messages from a JMS queue to a <a shape="rect" class="external-link" href="http://www.springramework.org" rel="nofollow">Spring</a> service. The route works in a synchronous fashion returning a response to the client.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1454973535454 {padding: 0px;}
-div.rbtoc1454973535454 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1454973535454 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1455009528305 {padding: 0px;}
+div.rbtoc1455009528305 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1455009528305 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style></p><div class="toc-macro rbtoc1454973535454">
+/*]]>*/</style></p><div class="toc-macro rbtoc1455009528305">
 <ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-TutorialonSpringRemotingwithJMS">Tutorial on Spring Remoting with JMS</a></li><li><a shape="rect" href="#BookInOnePage-Preface">Preface</a></li><li><a shape="rect" href="#BookInOnePage-Prerequisites">Prerequisites</a></li><li><a shape="rect" href="#BookInOnePage-Distribution">Distribution</a></li><li><a shape="rect" href="#BookInOnePage-About">About</a></li><li><a shape="rect" href="#BookInOnePage-CreatetheCamelProject">Create the Camel Project</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-UpdatethePOMwithDependencies">Update the POM with Dependencies</a></li></ul>
 </li><li><a shape="rect" href="#BookInOnePage-WritingtheServer">Writing the Server</a>
@@ -5840,11 +5840,11 @@ So we completed the last piece in the pi
 <p>This example has been removed from <strong>Camel 2.9</strong> onwards. Apache Axis 1.4 is a very old and unsupported framework. We encourage users to use <a shape="rect" href="cxf.html">CXF</a> instead of Axis.</p></div></div>
 
 <style type="text/css">/*<![CDATA[*/
-div.rbtoc1454973536694 {padding: 0px;}
-div.rbtoc1454973536694 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1454973536694 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1455009529659 {padding: 0px;}
+div.rbtoc1455009529659 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1455009529659 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style><div class="toc-macro rbtoc1454973536694">
+/*]]>*/</style><div class="toc-macro rbtoc1455009529659">
 <ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-TutorialusingAxis1.4withApacheCamel">Tutorial using Axis 1.4 with Apache Camel</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-Prerequisites">Prerequisites</a></li><li><a shape="rect" href="#BookInOnePage-Distribution">Distribution</a></li><li><a shape="rect" href="#BookInOnePage-Introduction">Introduction</a></li><li><a shape="rect" href="#BookInOnePage-SettinguptheprojecttorunAxis">Setting up the project to run Axis</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-Maven2">Maven 2</a></li><li><a shape="rect" href="#BookInOnePage-wsdl">wsdl</a></li><li><a shape="rect" href="#BookInOnePage-ConfiguringAxis">Configuring Axis</a></li><li><a shape="rect" href="#BookInOnePage-RunningtheExample">Running the Example</a></li></ul>
@@ -17294,11 +17294,11 @@ template.send(&quot;direct:alias-verify&
 ]]></script>
 </div></div><p></p><h3 id="BookInOnePage-SeeAlso.28">See Also</h3>
 <ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a shape="rect" href="component.html">Component</a></li><li><a shape="rect" href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting Started</a></li></ul><ul><li><a shape="rect" href="crypto.html">Crypto</a> Crypto is also available as a <a shape="rect" href="data-format.html">Data Format</a></li></ul> <h2 id="BookInOnePage-CXFComponent">CXF Component</h2><div class="confluence-information-macro confluence-information-macro-note"><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>When using CXF as a consumer, the <a shape="rect" href="cxf-bean-component.html">CXF Bean Component</a> allows you to factor out how message payloads are received from their processing as a RESTful or SOAP web service. This has the potential of using a multitude of transports to consume web 
 services. The bean component's configuration is also simpler and provides the fastest method to implement web services using Camel and CXF.</p></div></div><div class="confluence-information-macro confluence-information-macro-tip"><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>When using CXF in streaming modes (see DataFormat option), then also read about <a shape="rect" href="stream-caching.html">Stream caching</a>.</p></div></div><p>The <strong>cxf:</strong> component provides integration with <a shape="rect" href="http://cxf.apache.org">Apache CXF</a> for connecting to JAX-WS services hosted in CXF.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1454973543043 {padding: 0px;}
-div.rbtoc1454973543043 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1454973543043 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1455009575913 {padding: 0px;}
+div.rbtoc1455009575913 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1455009575913 li {margin-left: 0px;padding-left: 0px;}
 
-/*]]>*/</style></p><div class="toc-macro rbtoc1454973543043">
+/*]]>*/</style></p><div class="toc-macro rbtoc1455009575913">
 <ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-CXFComponent">CXF Component</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-URIformat">URI format</a></li><li><a shape="rect" href="#BookInOnePage-Options">Options</a>
 <ul class="toc-indentation"><li><a shape="rect" href="#BookInOnePage-Thedescriptionsofthedataformats">The descriptions of the dataformats</a>
@@ -26776,7 +26776,7 @@ from(&quot;seda:someEndpoint&quot;).
     &lt;!-- use the same version as your Camel core version --&gt;
 &lt;/dependency&gt;
 ]]></script>
-</div></div><p>From Camel 2.9 onwards the <a shape="rect" href="validation.html">Validation</a> component is provided directly in the camel-core.</p><h3 id="BookInOnePage-Options.77">Options</h3><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Option</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">resourceResolverFactory</td><td colspan="1" rowspan="1" class="confluenceTd">DefaultValidatorResourceResolverFactory</td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17</strong>: Reference to a <code>org.apache.camel.component.validator.ValidatorResourceResolverFactory </code>which creates a resource resolver per endpoint<code>. </code><span>The default implementation returns an instance of <code><span>org.apache.
 camel.component.validator.</span>DefaultLSResourceResolver </code></span><span><span>which reads the schema files from the classpath and the file system. This option instead of the option <code>resourceResolver</code> shall be used when the resource resolver depends on the resource URI of the root schema document specified in the endpoint. This option is also available on the validator component, so that you can set the resource resolver factory only once for all endpoints.</span></span></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>resourceResolver</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong> Reference to a <code>org.w3c.dom.ls.LSResourceResolver</code> in the <a shape="rect" href="registry.html">Registry</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useDom</code></p></td><td colspan="1" rowspan="1
 " class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Whether <code>DOMSource</code>/<code>DOMResult</code> or <code>SaxSource</code>/<code>SaxResult</code> should be used by the validator.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useSharedSchema</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> Whether the <code>Schema</code> instance should be shared or not. This option is introduced to work around a <a shape="rect" class="external-link" href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6773084" rel="nofollow">JDK 1.6.x bug</a>. Xerces should not have this issue.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>failOnNullBody</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1"
  class="confluenceTd"><p><strong>Camel 2.9.5/2.10.3:</strong> Whether to fail if no body exists.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>headerName</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.11:</strong> To validate against a header instead of the message body.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>failOnNullHeader</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.11:</strong> Whether to fail if no header exists when validating against a header.</p></td></tr></tbody></table></div></div><h3 id="BookInOnePage-Example.30">Example</h3><p>The following <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/camel/trunk/components/camel-spring/src/test/resources/org/apache/
 camel/component/validator/camelContext.xml">example</a> shows how to configure a route from endpoint <strong>direct:start</strong> which then goes to one of two endpoints, either <strong>mock:valid</strong> or <strong>mock:invalid</strong> based on whether or not the XML matches the given schema (which is supplied on the classpath).</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>From Camel 2.9 onwards the <a shape="rect" href="validation.html">Validation</a> component is provided directly in the camel-core.</p><h3 id="BookInOnePage-Options.77">Options</h3><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Option</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">resourceResolverFactory</td><td colspan="1" rowspan="1" class="confluenceTd">DefaultValidatorResourceResolverFactory</td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17</strong>: Reference to a <code>org.apache.camel.component.validator.ValidatorResourceResolverFactory </code>which creates a resource resolver per endpoint<code>. </code><span>The default implementation creates an instance of <code><span>org.apache.
 camel.component.validator.</span>DefaultLSResourceResolver per endpoint </code></span><span><span>which creates the default resource resolver <code><span>org.apache.camel.component.validator.</span>DefaultLSResourceResolver. The default resource resolver</code> reads the schema files from the classpath and the file system. This option instead of the option <code>resourceResolver</code> shall be used when the resource resolver depends on the resource URI of the root schema document specified in the endpoint; for example, if you want to extend the default resource resolver. This option is also available on the validator component, so that you can set the resource resolver factory only once for all endpoints.</span></span></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>resourceResolver</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong> Refere
 nce to a <code>org.w3c.dom.ls.LSResourceResolver</code> in the <a shape="rect" href="registry.html">Registry</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useDom</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Whether <code>DOMSource</code>/<code>DOMResult</code> or <code>SaxSource</code>/<code>SaxResult</code> should be used by the validator.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useSharedSchema</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> Whether the <code>Schema</code> instance should be shared or not. This option is introduced to work around a <a shape="rect" class="external-link" href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6773084" rel="nofollow">JDK 1.6.x bug</a>. Xerces s
 hould not have this issue.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>failOnNullBody</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9.5/2.10.3:</strong> Whether to fail if no body exists.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>headerName</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.11:</strong> To validate against a header instead of the message body.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>failOnNullHeader</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.11:</strong> Whether to fail if no header exists when validating against a header.</p></td><
 /tr></tbody></table></div></div><h3 id="BookInOnePage-Example.30">Example</h3><p>The following <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/camel/trunk/components/camel-spring/src/test/resources/org/apache/camel/component/validator/camelContext.xml">example</a> shows how to configure a route from endpoint <strong>direct:start</strong> which then goes to one of two endpoints, either <strong>mock:valid</strong> or <strong>mock:invalid</strong> based on whether or not the XML matches the given schema (which is supplied on the classpath).</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
 &lt;route&gt;
     &lt;from uri=&quot;direct:start&quot;/&gt;
@@ -27048,7 +27048,7 @@ from(&quot;activemq:My.Queue&quot;).
     &lt;!-- use the same version as your Camel core version --&gt;
 &lt;/dependency&gt;
 ]]></script>
-</div></div><p>From Camel 2.9 onwards the <a shape="rect" href="xslt.html">XSLT</a> component is provided directly in the camel-core.</p><h3 id="BookInOnePage-Options.81">Options</h3><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default Value</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>converter</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Option to override default <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/converter/jaxp/XmlConverter.html">XmlConverter</a>. Will lookup for the converter in the <a shape="rect" href="registry.html">Registry</
 a>. The provided converted must be of type org.apache.camel.converter.jaxp.XmlConverter.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>transformerFactory</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Option to override default <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/transform/TransformerFactory.html" rel="nofollow">TransformerFactory</a>. Will lookup for the transformerFactory in the <a shape="rect" href="registry.html">Registry</a>. The provided transformer factory must be of type javax.xml.transform.TransformerFactory.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>transformerFactoryClass</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Option to override default <a shape="rect" c
 lass="external-link" href="http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/transform/TransformerFactory.html" rel="nofollow">TransformerFactory</a>. Will create a TransformerFactoryClass instance and set it to the converter.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>uriResolver</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.3</strong>: Allows you to use a custom <code>javax.xml.transformation.URIResolver</code>. Camel will by default use its own implementation <code>org.apache.camel.builder.xml.XsltUriResolver</code> which is capable of loading from classpath.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>resultHandlerFactory</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> Allows you t
 o use a custom <code>org.apache.camel.builder.xml.ResultHandlerFactory</code> which is capable of using custom <code>org.apache.camel.builder.xml.ResultHandler</code> types.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>failOnNullBody</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> Whether or not to throw an exception if the input body is null.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>deleteOutputFile</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.6:</strong> If you have <code>output=file</code> then this option dictates whether or not the output file should be deleted when the <a shape="rect" href="exchange.html">Exchange</a> is done processing. For example suppose the output file is 
 a temporary file, then it can be a good idea to delete it after use.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>output</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>string</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> Option to specify which output type to use. Possible values are: <code>string, bytes, DOM, file</code>. The first three options are all in memory based, where as <code>file</code> is streamed directly to a <code>java.io.File</code>. For <code>file</code> you <strong>must</strong> specify the filename in the IN header with the key <code>Exchange.XSLT_FILE_NAME</code> which is also <code>CamelXsltFileName</code>. Also any paths leading to the filename must be created beforehand, otherwise an exception is thrown at runtime.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>contentCache</code></p></td><td colspan="1" rowspan="1" class="conflu
 enceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.6:</strong> Cache for the resource content (the stylesheet file) when it is loaded. If set to <code>false</code> Camel will reload the stylesheet file on each message processing. This is good for development. <br clear="none"> Note: from <strong>Camel 2.9</strong> a cached stylesheet can be forced to reload at runtime via JMX using the <code>clearCachedStylesheet</code> operation.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>allowStAX</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.8.3/2.9:</strong> Whether to allow using StAX as the <code>javax.xml.transform.Source</code>. The option is default <code>false</code> in Camel 2.11.3/2.12.2 or older. And default <code>true</code> in Camel 2.11.4/2.12.3 onwards.</p></td></tr><tr><td colspan="1" rowspan="1
 " class="confluenceTd"><p><code>transformerCacheSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9.3/2.10.1:</strong> The number of <code>javax.xml.transform.Transformer</code> object that are cached for reuse to avoid calls to <code>Template.newTransformer()</code>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>saxon</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.11:</strong> Whether to use Saxon as the <code>transformerFactoryClass</code>. If enabled then the class <code>net.sf.saxon.TransformerFactoryImpl</code>. You would need to add Saxon to the classpath.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">errorListener</td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1"
  class="confluenceTd"><strong>Camel 2.14:</strong> Allows to configure to use a custom <code>javax.xml.transform.ErrorListener</code>. Beware when doing this then the default error listener which captures any errors or fatal errors and store information on the Exchange as properties is not in use. So only use this option for special use-cases.</td></tr></tbody></table></div></div><h3 id="BookInOnePage-UsingXSLTendpoints">Using XSLT endpoints</h3><p>For example you could use something like</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>From Camel 2.9 onwards the <a shape="rect" href="xslt.html">XSLT</a> component is provided directly in the camel-core.</p><h3 id="BookInOnePage-Options.81">Options</h3><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default Value</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>converter</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Option to override default <a shape="rect" class="external-link" href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/converter/jaxp/XmlConverter.html">XmlConverter</a>. Will lookup for the converter in the <a shape="rect" href="registry.html">Registry</
 a>. The provided converted must be of type org.apache.camel.converter.jaxp.XmlConverter.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>transformerFactory</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Option to override default <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/transform/TransformerFactory.html" rel="nofollow">TransformerFactory</a>. Will lookup for the transformerFactory in the <a shape="rect" href="registry.html">Registry</a>. The provided transformer factory must be of type javax.xml.transform.TransformerFactory.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>transformerFactoryClass</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Option to override default <a shape="rect" c
 lass="external-link" href="http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/transform/TransformerFactory.html" rel="nofollow">TransformerFactory</a>. Will create a TransformerFactoryClass instance and set it to the converter.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><code>uriResolverFactory</code></td><td colspan="1" rowspan="1" class="confluenceTd"><code>DefaultXsltUriResolverFactory</code></td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17</strong>: <span style="color: rgb(51,51,51);">&#160;Reference to a&#160;</span><code style="text-align: left;">org.apache.camel.component.</code><code style="text-align: left;">xslt</code><code style="text-align: left;">.</code><span style="color: rgb(51,51,51);"><code>XsltUriResolverFactory</code> which creates an URI resolver per endpoint</span><code style="text-align: left;">.</code><span style="color: rgb(51,51,51);">The default implementation returns an instance of&#160;<code><span>org.apache.c
 amel.component.xslt.</span></code></span><span style="color: rgb(51,51,51);"><span><code>DefaultXsltUriResolverFactory</code> which creates the default URI resolver&#160;<span style="color: rgb(51,51,51);"><span><span style="color: rgb(51,51,51);"><code><span>org.apache.camel.builder.</span><span>xml</span></code></span>.XsltUriResolver</span></span> per endpoint. The default URI resolver reads XSLT documents from the classpath and the file system. This option instead of the option <code>uriResolver</code>&#160;shall be used when the URI resolver depends on the resource URI of the root XSLT document specified in the endpoint; for example, if you want to extend the default URI resolver. This option is also available on the XSLT component, so that you can set the resource resolver factory only once for all endpoints.</span></span></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>uriResolver</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>
 null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.3</strong>: Allows you to use a custom <code>javax.xml.transformation.URIResolver</code>. Camel will by default use its own implementation <code>org.apache.camel.builder.xml.XsltUriResolver</code> which is capable of loading from classpath.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>resultHandlerFactory</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> Allows you to use a custom <code>org.apache.camel.builder.xml.ResultHandlerFactory</code> which is capable of using custom <code>org.apache.camel.builder.xml.ResultHandler</code> types.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>failOnNullBody</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" cl
 ass="confluenceTd"><p><strong>Camel 2.3:</strong> Whether or not to throw an exception if the input body is null.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>deleteOutputFile</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.6:</strong> If you have <code>output=file</code> then this option dictates whether or not the output file should be deleted when the <a shape="rect" href="exchange.html">Exchange</a> is done processing. For example suppose the output file is a temporary file, then it can be a good idea to delete it after use.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>output</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>string</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> Option to specify which output type to use. Possible values a
 re: <code>string, bytes, DOM, file</code>. The first three options are all in memory based, where as <code>file</code> is streamed directly to a <code>java.io.File</code>. For <code>file</code> you <strong>must</strong> specify the filename in the IN header with the key <code>Exchange.XSLT_FILE_NAME</code> which is also <code>CamelXsltFileName</code>. Also any paths leading to the filename must be created beforehand, otherwise an exception is thrown at runtime.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>contentCache</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.6:</strong> Cache for the resource content (the stylesheet file) when it is loaded. If set to <code>false</code> Camel will reload the stylesheet file on each message processing. This is good for development. <br clear="none"> Note: from <strong>Camel 2.9</strong> a cached styleshe
 et can be forced to reload at runtime via JMX using the <code>clearCachedStylesheet</code> operation.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>allowStAX</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.8.3/2.9:</strong> Whether to allow using StAX as the <code>javax.xml.transform.Source</code>. The option is default <code>false</code> in Camel 2.11.3/2.12.2 or older. And default <code>true</code> in Camel 2.11.4/2.12.3 onwards.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>transformerCacheSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9.3/2.10.1:</strong> The number of <code>javax.xml.transform.Transformer</code> object that are cached for reuse to avoid calls to <code>Template.newTransformer()</code>.</p></
 td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>saxon</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.11:</strong> Whether to use Saxon as the <code>transformerFactoryClass</code>. If enabled then the class <code>net.sf.saxon.TransformerFactoryImpl</code>. You would need to add Saxon to the classpath.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">errorListener</td><td colspan="1" rowspan="1" class="confluenceTd">&#160;</td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.14:</strong> Allows to configure to use a custom <code>javax.xml.transform.ErrorListener</code>. Beware when doing this then the default error listener which captures any errors or fatal errors and store information on the Exchange as properties is not in use. So only use this option for special use-cases.</td></tr></tbody></table></div></div><h3 
 id="BookInOnePage-UsingXSLTendpoints">Using XSLT endpoints</h3><p>For example you could use something like</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[from(&quot;activemq:My.Queue&quot;).
   to(&quot;xslt:com/acme/mytransform.xsl&quot;);
 ]]></script>

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

Modified: websites/production/camel/content/validation.html
==============================================================================
--- websites/production/camel/content/validation.html (original)
+++ websites/production/camel/content/validation.html Tue Feb  9 09:21:07 2016
@@ -97,7 +97,7 @@
     &lt;!-- use the same version as your Camel core version --&gt;
 &lt;/dependency&gt;
 ]]></script>
-</div></div><p>From Camel 2.9 onwards the <a shape="rect" href="validation.html">Validation</a> component is provided directly in the camel-core.</p><h3 id="Validation-Options">Options</h3><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Option</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">resourceResolverFactory</td><td colspan="1" rowspan="1" class="confluenceTd">DefaultValidatorResourceResolverFactory</td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17</strong>: Reference to a <code>org.apache.camel.component.validator.ValidatorResourceResolverFactory </code>which creates a resource resolver per endpoint<code>. </code><span>The default implementation returns an instance of <code><span>org.apache.camel.
 component.validator.</span>DefaultLSResourceResolver </code></span><span><span>which reads the schema files from the classpath and the file system. This option instead of the option <code>resourceResolver</code> shall be used when the resource resolver depends on the resource URI of the root schema document specified in the endpoint. This option is also available on the validator component, so that you can set the resource resolver factory only once for all endpoints.</span></span></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>resourceResolver</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong> Reference to a <code>org.w3c.dom.ls.LSResourceResolver</code> in the <a shape="rect" href="registry.html">Registry</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useDom</code></p></td><td colspan="1" rowspan="1" clas
 s="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Whether <code>DOMSource</code>/<code>DOMResult</code> or <code>SaxSource</code>/<code>SaxResult</code> should be used by the validator.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useSharedSchema</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> Whether the <code>Schema</code> instance should be shared or not. This option is introduced to work around a <a shape="rect" class="external-link" href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6773084" rel="nofollow">JDK 1.6.x bug</a>. Xerces should not have this issue.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>failOnNullBody</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class
 ="confluenceTd"><p><strong>Camel 2.9.5/2.10.3:</strong> Whether to fail if no body exists.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>headerName</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.11:</strong> To validate against a header instead of the message body.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>failOnNullHeader</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.11:</strong> Whether to fail if no header exists when validating against a header.</p></td></tr></tbody></table></div></div><h3 id="Validation-Example">Example</h3><p>The following <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/camel/trunk/components/camel-spring/src/test/resources/org/apache/camel/compon
 ent/validator/camelContext.xml">example</a> shows how to configure a route from endpoint <strong>direct:start</strong> which then goes to one of two endpoints, either <strong>mock:valid</strong> or <strong>mock:invalid</strong> based on whether or not the XML matches the given schema (which is supplied on the classpath).</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>From Camel 2.9 onwards the <a shape="rect" href="validation.html">Validation</a> component is provided directly in the camel-core.</p><h3 id="Validation-Options">Options</h3><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Option</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">resourceResolverFactory</td><td colspan="1" rowspan="1" class="confluenceTd">DefaultValidatorResourceResolverFactory</td><td colspan="1" rowspan="1" class="confluenceTd"><strong>Camel 2.17</strong>: Reference to a <code>org.apache.camel.component.validator.ValidatorResourceResolverFactory </code>which creates a resource resolver per endpoint<code>. </code><span>The default implementation creates an instance of <code><span>org.apache.camel.
 component.validator.</span>DefaultLSResourceResolver per endpoint </code></span><span><span>which creates the default resource resolver <code><span>org.apache.camel.component.validator.</span>DefaultLSResourceResolver. The default resource resolver</code> reads the schema files from the classpath and the file system. This option instead of the option <code>resourceResolver</code> shall be used when the resource resolver depends on the resource URI of the root schema document specified in the endpoint; for example, if you want to extend the default resource resolver. This option is also available on the validator component, so that you can set the resource resolver factory only once for all endpoints.</span></span></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>resourceResolver</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9:</strong> Reference to
  a <code>org.w3c.dom.ls.LSResourceResolver</code> in the <a shape="rect" href="registry.html">Registry</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useDom</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Whether <code>DOMSource</code>/<code>DOMResult</code> or <code>SaxSource</code>/<code>SaxResult</code> should be used by the validator.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useSharedSchema</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.3:</strong> Whether the <code>Schema</code> instance should be shared or not. This option is introduced to work around a <a shape="rect" class="external-link" href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6773084" rel="nofollow">JDK 1.6.x bug</a>. Xerces should 
 not have this issue.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>failOnNullBody</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.9.5/2.10.3:</strong> Whether to fail if no body exists.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>headerName</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.11:</strong> To validate against a header instead of the message body.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>failOnNullHeader</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.11:</strong> Whether to fail if no header exists when validating against a header.</p></td></tr></
 tbody></table></div></div><h3 id="Validation-Example">Example</h3><p>The following <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/camel/trunk/components/camel-spring/src/test/resources/org/apache/camel/component/validator/camelContext.xml">example</a> shows how to configure a route from endpoint <strong>direct:start</strong> which then goes to one of two endpoints, either <strong>mock:valid</strong> or <strong>mock:invalid</strong> based on whether or not the XML matches the given schema (which is supplied on the classpath).</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
 &lt;route&gt;
     &lt;from uri=&quot;direct:start&quot;/&gt;



Mime
View raw message