You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by bu...@apache.org on 2016/01/16 10:25:56 UTC
svn commit: r977844 [1/2] - in /websites/production/camel/content:
book-component-appendix.html book-in-one-page.html cache/main.pageCache
camel-2170-release.html cometd.html validation.html
Author: buildbot
Date: Sat Jan 16 09:25:55 2016
New Revision: 977844
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/camel-2170-release.html
websites/production/camel/content/cometd.html
websites/production/camel/content/validation.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 Sat Jan 16 09:25:55 2016
@@ -712,7 +712,7 @@ browse:someName[?options]
<pre>cometd://localhost:8080/service/mychannel
cometds://localhost:8443/service/mychannel
</pre>
-</div></div><p>where <code>cometds:</code> represents an SSL configured endpoint.</p><h3 id="BookComponentAppendix-Options.5">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>resourceBase</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar. Notice this option has been renamed to <code>baseResource</code>
from <strong>Camel 2.7</strong> onwards.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>baseResource</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.7:</strong> The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>timeout</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>240000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The server side poll timeout in milliseconds. This is how long the server will hold a reconnect request before responding.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>interval
</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The client side poll timeout in milliseconds. How long a client will wait between reconnects</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>maxInterval</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>30000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The max client side poll timeout in milliseconds. A client will be removed if a connection is not received in this time.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>multiFrameInterval</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1500</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The client side poll timeout, if multiple connections are detected from the same browser.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>jso
nCommented</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <code>true</code>, the server will accept JSON wrapped in a comment and will generate JSON wrapped in a comment. This is a defence against Ajax Hijacking.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>logLevel</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code>=none, <code>1</code>=info, <code>2</code>=debug.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>crossOriginFilterOn</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.10:</strong> If <code>true</code>, the server will support for cross-domain filtering</p></td></tr><tr><td colspan="1" rowspan="1" class
="confluenceTd"><p><code>allowedOrigins</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>*</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.10:</strong> The origins domain that support to cross, if the <code>crosssOriginFilterOn</code> is <code>true</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>filterPath</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.10:</strong> The filterPath will be used by the CrossOriginFilter, if the <code>crosssOriginFilterOn</code> is <code>true</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>disconnectLocalSession</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.10.5/2.11.1: (Producer only)</strong>: Whether to disconne
ct local sessions after publishing a message to its channel. Disconnecting local session is needed as they are not swept by default by CometD, and therefore you can run out of memory.</p></td></tr></tbody></table></div></div><p>You can append query options to the URI in the following format, <code>?option=value&option=value&...</code></p><p>Here is some examples on How to pass the parameters</p><p>For file (for webapp resources located in the Web Application directory --> cometd://localhost:8080?resourceBase=file./webapp<br clear="none"> For classpath (when by example the web resources are packaged inside the webapp folder --> cometd://localhost:8080?resourceBase=classpath:webapp</p><h3 id="BookComponentAppendix-Authentication">Authentication</h3><p><strong>Available as of Camel 2.8</strong></p><p>You can configure custom <code>SecurityPolicy</code> and <code>Extension</code>'s to the <code>CometdComponent</code> which allows you to use authentication as <a shape="rect
" class="external-link" href="http://cometd.org/documentation/howtos/authentication" rel="nofollow">documented here</a></p><h3 id="BookComponentAppendix-SettingupSSLforCometdComponent">Setting up SSL for Cometd Component</h3><h4 id="BookComponentAppendix-UsingtheJSSEConfigurationUtility">Using the JSSE Configuration Utility</h4><p>As of Camel 2.9, the Cometd component supports SSL/TLS configuration through the <a shape="rect" href="camel-configuration-utilities.html">Camel JSSE Configuration Utility</a>.  This utility greatly decreases the amount of component specific code you need to write and is configurable at the endpoint and component levels.  The following examples demonstrate how to use the utility with the Cometd component. You need to configure SSL on the CometdComponent.</p><h5 id="BookComponentAppendix-Programmaticconfigurationofthecomponent">Programmatic configuration of the component</h5><div class="code panel pdl" style="border-width: 1px;"><div class="codeCo
ntent panelContent pdl">
+</div></div><p>where <code>cometds:</code> represents an SSL configured endpoint.</p><h3 id="BookComponentAppendix-Options.5">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>resourceBase</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar. Notice this option has been renamed to <code>baseResource</code>
from <strong>Camel 2.7</strong> onwards.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>baseResource</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.7:</strong> The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>timeout</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>240000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The server side poll timeout in milliseconds. This is how long the server will hold a reconnect request before responding.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>interval
</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The client side poll timeout in milliseconds. How long a client will wait between reconnects</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>maxInterval</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>30000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The max client side poll timeout in milliseconds. A client will be removed if a connection is not received in this time.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>multiFrameInterval</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1500</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The client side poll timeout, if multiple connections are detected from the same browser.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>jso
nCommented</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <code>true</code>, the server will accept JSON wrapped in a comment and will generate JSON wrapped in a comment. This is a defence against Ajax Hijacking.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>logLevel</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code>=none, <code>1</code>=info, <code>2</code>=debug.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>crossOriginFilterOn</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.10:</strong> If <code>true</code>, the server will support for cross-domain filtering</p></td></tr><tr><td colspan="1" rowspan="1" class
="confluenceTd"><p><code>allowedOrigins</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>*</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.10:</strong> The origins domain that support to cross, if the <code>crosssOriginFilterOn</code> is <code>true</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>filterPath</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.10:</strong> The filterPath will be used by the CrossOriginFilter, if the <code>crosssOriginFilterOn</code> is <code>true</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>disconnectLocalSession</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.10.5/2.11.1: (Producer only)</strong>: Whether to disconnect local se
ssions after publishing a message to its channel. Disconnecting local session is needed as they are not swept by default by CometD, and therefore you can run out of memory. In Camel 2.16.1/2.15.5 or older the default value is true. From newer versions the default value is false.</p></td></tr></tbody></table></div></div><p>You can append query options to the URI in the following format, <code>?option=value&option=value&...</code></p><p>Here is some examples on How to pass the parameters</p><p>For file (for webapp resources located in the Web Application directory --> cometd://localhost:8080?resourceBase=file./webapp<br clear="none"> For classpath (when by example the web resources are packaged inside the webapp folder --> cometd://localhost:8080?resourceBase=classpath:webapp</p><h3 id="BookComponentAppendix-Authentication">Authentication</h3><p><strong>Available as of Camel 2.8</strong></p><p>You can configure custom <code>SecurityPolicy</code> and <code>Extension</code
>'s to the <code>CometdComponent</code> which allows you to use authentication as <a shape="rect" class="external-link" href="http://cometd.org/documentation/howtos/authentication" rel="nofollow">documented here</a></p><h3 id="BookComponentAppendix-SettingupSSLforCometdComponent">Setting up SSL for Cometd Component</h3><h4 id="BookComponentAppendix-UsingtheJSSEConfigurationUtility">Using the JSSE Configuration Utility</h4><p>As of Camel 2.9, the Cometd component supports SSL/TLS configuration through the <a shape="rect" href="camel-configuration-utilities.html">Camel JSSE Configuration Utility</a>.  This utility greatly decreases the amount of component specific code you need to write and is configurable at the endpoint and component levels.  The following examples demonstrate how to use the utility with the Cometd component. You need to configure SSL on the CometdComponent.</p><h5 id="BookComponentAppendix-Programmaticconfigurationofthecomponent">Programmatic configuratio
n of the component</h5><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[KeyStoreParameters ksp = new KeyStoreParameters();
ksp.setResource("/users/home/server/keystore.jks");
ksp.setPassword("keystorePassword");
@@ -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.rbtoc1452356288507 {padding: 0px;}
-div.rbtoc1452356288507 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1452356288507 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1452936133220 {padding: 0px;}
+div.rbtoc1452936133220 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1452936133220 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1452356288507">
+/*]]>*/</style></p><div class="toc-macro rbtoc1452936133220">
<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>
@@ -10485,53 +10485,18 @@ from("seda:someEndpoint").
</route>
]]></script>
</div></div><p></p><h3 id="BookComponentAppendix-SeeAlso.65">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="quartz.html">Quartz</a></li></ul> <h2 id="BookComponentAppendix-ValidationComponent">Validation Component</h2>
-
-<p>The Validation component performs XML validation of the message body using the JAXP Validation API and based on any of the supported XML schema languages, which defaults to <a shape="rect" class="external-link" href="http://www.w3.org/XML/Schema" rel="nofollow">XML Schema</a> </p>
-
-<p>Note that the <a shape="rect" href="jing.html">Jing</a> component also supports the following useful schema languages:</p>
-
-<ul><li><a shape="rect" class="external-link" href="http://relaxng.org/compact-tutorial-20030326.html" rel="nofollow">RelaxNG Compact Syntax</a></li><li><a shape="rect" class="external-link" href="http://relaxng.org/" rel="nofollow">RelaxNG XML Syntax</a></li></ul>
-
-
-<p>The <a shape="rect" href="msv.html">MSV</a> component also supports <a shape="rect" class="external-link" href="http://relaxng.org/" rel="nofollow">RelaxNG XML Syntax</a>.</p>
-
-<h3 id="BookComponentAppendix-URIformat.71">URI format</h3>
-
-<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[
-validator:someLocalOrRemoteResource
+<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="quartz.html">Quartz</a></li></ul> <h2 id="BookComponentAppendix-ValidationComponent">Validation Component</h2><p>The Validation component performs XML validation of the message body using the JAXP Validation API and based on any of the supported XML schema languages, which defaults to <a shape="rect" class="external-link" href="http://www.w3.org/XML/Schema" rel="nofollow">XML Schema</a></p><p>Note that the <a shape="rect" href="jing.html">Jing</a> component also supports the following useful schema languages:</p><ul><li><a shape="rect" class="external-link" href="http://relaxng.org/compact-tutorial-20030326.html" rel="nofollow">RelaxNG Compact Syntax</a></li><li><a shape="rect" class
="external-link" href="http://relaxng.org/" rel="nofollow">RelaxNG XML Syntax</a></li></ul><p>The <a shape="rect" href="msv.html">MSV</a> component also supports <a shape="rect" class="external-link" href="http://relaxng.org/" rel="nofollow">RelaxNG XML Syntax</a>.</p><h3 id="BookComponentAppendix-URIformat.71">URI format</h3><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[validator:someLocalOrRemoteResource
]]></script>
-</div></div>
-
-<p>Where <strong>someLocalOrRemoteResource</strong> is some URL to a local resource on the classpath or a full URL to a remote resource or resource on the file system which contains the XSD to validate against. For example:</p>
-
-<ul><li><code>msv:org/foo/bar.xsd</code></li><li><code>msv:file:../foo/bar.xsd</code></li><li><code>msv:<a shape="rect" class="external-link" href="http://acme.com/cheese.xsd" rel="nofollow">http://acme.com/cheese.xsd</a></code></li><li><code>validator:com/mypackage/myschema.xsd</code></li></ul>
-
-
-<p>Maven users will need to add the following dependency to their <code>pom.xml</code> for this component when using <strong>Camel 2.8</strong> or older:</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[
-<dependency>
+</div></div><p>Where <strong>someLocalOrRemoteResource</strong> is some URL to a local resource on the classpath or a full URL to a remote resource or resource on the file system which contains the XSD to validate against. For example:</p><ul><li><code>msv:org/foo/bar.xsd</code></li><li><code>msv:file:../foo/bar.xsd</code></li><li><code>msv:<a shape="rect" class="external-link" href="http://acme.com/cheese.xsd" rel="nofollow">http://acme.com/cheese.xsd</a></code></li><li><code>validator:com/mypackage/myschema.xsd</code></li></ul><p>Maven users will need to add the following dependency to their <code>pom.xml</code> for this component when using <strong>Camel 2.8</strong> or older:</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[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-spring</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
]]></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"><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">
+</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"><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[
<route>
<from uri="direct:start"/>
@@ -10548,9 +10513,7 @@ validator:someLocalOrRemoteResource
</doTry>
</route>
]]></script>
-</div></div>
-
-<h3 id="BookComponentAppendix-SeeAlso.66">See Also</h3>
+</div></div><h3 id="BookComponentAppendix-Advanced:JMXmethodclearCachedSchema">Advanced: JMX method clearCachedSchema</h3><p>Since <strong>Camel 2.17</strong>, you can force that the cached schema in the validator endpoint is cleared and reread with the next process call with the JMX operation <code>clearCachedSchema. </code>You can also use this method to programmatically clear the cache. This method is available on the <code>ValidatorEndpoint </code>class<code>.</code></p><p></p><h3 id="BookComponentAppendix-SeeAlso.66">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> <h2 id="BookComponentAppendix-Velocity">Velocity</h2><p>The <strong>velocity:</strong> component allows you to process a message using an <a shape="rect" class="external-link" href="http://velocity.apache.org/">Apache Velocity</a> template. This can be ideal when using <a shape="rect" href="templating.html">Templating</a> to generate responses for requests.</p><p>Maven users will need to add the following dependency to their <code>pom.xml</code> for this component:</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[<dependency>
<groupId>org.apache.camel</groupId>
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 Sat Jan 16 09:25:55 2016
@@ -3729,11 +3729,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> </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.rbtoc1452828063998 {padding: 0px;}
-div.rbtoc1452828063998 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1452828063998 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1452936151532 {padding: 0px;}
+div.rbtoc1452936151532 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1452936151532 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1452828063998">
+/*]]>*/</style></p><div class="toc-macro rbtoc1452936151532">
<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>
@@ -5838,11 +5838,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.rbtoc1452828064679 {padding: 0px;}
-div.rbtoc1452828064679 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1452828064679 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1452936152877 {padding: 0px;}
+div.rbtoc1452936152877 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1452936152877 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style><div class="toc-macro rbtoc1452828064679">
+/*]]>*/</style><div class="toc-macro rbtoc1452936152877">
<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>
@@ -16988,7 +16988,7 @@ browse:someName[?options]
<pre>cometd://localhost:8080/service/mychannel
cometds://localhost:8443/service/mychannel
</pre>
-</div></div><p>where <code>cometds:</code> represents an SSL configured endpoint.</p><h3 id="BookInOnePage-Options.26">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>resourceBase</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar. Notice this option has been renamed to <code>baseResource</code> from <
strong>Camel 2.7</strong> onwards.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>baseResource</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.7:</strong> The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>timeout</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>240000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The server side poll timeout in milliseconds. This is how long the server will hold a reconnect request before responding.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>interval</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The client side poll timeout in milliseconds. How long a client will wait between reconnects</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>maxInterval</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>30000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The max client side poll timeout in milliseconds. A client will be removed if a connection is not received in this time.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>multiFrameInterval</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1500</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The client side poll timeout, if multiple connections are detected from the same browser.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>jsonCommen
ted</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <code>true</code>, the server will accept JSON wrapped in a comment and will generate JSON wrapped in a comment. This is a defence against Ajax Hijacking.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>logLevel</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code>=none, <code>1</code>=info, <code>2</code>=debug.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>crossOriginFilterOn</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.10:</strong> If <code>true</code>, the server will support for cross-domain filtering</p></td></tr><tr><td colspan="1" rowspan="1" class="confl
uenceTd"><p><code>allowedOrigins</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>*</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.10:</strong> The origins domain that support to cross, if the <code>crosssOriginFilterOn</code> is <code>true</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>filterPath</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.10:</strong> The filterPath will be used by the CrossOriginFilter, if the <code>crosssOriginFilterOn</code> is <code>true</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>disconnectLocalSession</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.10.5/2.11.1: (Producer only)</strong>: Whether to disconnect loca
l sessions after publishing a message to its channel. Disconnecting local session is needed as they are not swept by default by CometD, and therefore you can run out of memory.</p></td></tr></tbody></table></div></div><p>You can append query options to the URI in the following format, <code>?option=value&option=value&...</code></p><p>Here is some examples on How to pass the parameters</p><p>For file (for webapp resources located in the Web Application directory --> cometd://localhost:8080?resourceBase=file./webapp<br clear="none"> For classpath (when by example the web resources are packaged inside the webapp folder --> cometd://localhost:8080?resourceBase=classpath:webapp</p><h3 id="BookInOnePage-Authentication">Authentication</h3><p><strong>Available as of Camel 2.8</strong></p><p>You can configure custom <code>SecurityPolicy</code> and <code>Extension</code>'s to the <code>CometdComponent</code> which allows you to use authentication as <a shape="rect" class="extern
al-link" href="http://cometd.org/documentation/howtos/authentication" rel="nofollow">documented here</a></p><h3 id="BookInOnePage-SettingupSSLforCometdComponent">Setting up SSL for Cometd Component</h3><h4 id="BookInOnePage-UsingtheJSSEConfigurationUtility">Using the JSSE Configuration Utility</h4><p>As of Camel 2.9, the Cometd component supports SSL/TLS configuration through the <a shape="rect" href="camel-configuration-utilities.html">Camel JSSE Configuration Utility</a>.  This utility greatly decreases the amount of component specific code you need to write and is configurable at the endpoint and component levels.  The following examples demonstrate how to use the utility with the Cometd component. You need to configure SSL on the CometdComponent.</p><h5 id="BookInOnePage-Programmaticconfigurationofthecomponent">Programmatic configuration of the component</h5><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p>where <code>cometds:</code> represents an SSL configured endpoint.</p><h3 id="BookInOnePage-Options.26">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>resourceBase</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar. Notice this option has been renamed to <code>baseResource</code> from <
strong>Camel 2.7</strong> onwards.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>baseResource</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.7:</strong> The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>timeout</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>240000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The server side poll timeout in milliseconds. This is how long the server will hold a reconnect request before responding.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>interval</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The client side poll timeout in milliseconds. How long a client will wait between reconnects</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>maxInterval</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>30000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The max client side poll timeout in milliseconds. A client will be removed if a connection is not received in this time.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>multiFrameInterval</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1500</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The client side poll timeout, if multiple connections are detected from the same browser.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>jsonCommen
ted</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <code>true</code>, the server will accept JSON wrapped in a comment and will generate JSON wrapped in a comment. This is a defence against Ajax Hijacking.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>logLevel</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code>=none, <code>1</code>=info, <code>2</code>=debug.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>crossOriginFilterOn</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.10:</strong> If <code>true</code>, the server will support for cross-domain filtering</p></td></tr><tr><td colspan="1" rowspan="1" class="confl
uenceTd"><p><code>allowedOrigins</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>*</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.10:</strong> The origins domain that support to cross, if the <code>crosssOriginFilterOn</code> is <code>true</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>filterPath</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.10:</strong> The filterPath will be used by the CrossOriginFilter, if the <code>crosssOriginFilterOn</code> is <code>true</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>disconnectLocalSession</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Camel 2.10.5/2.11.1: (Producer only)</strong>: Whether to disconnect local sessions
after publishing a message to its channel. Disconnecting local session is needed as they are not swept by default by CometD, and therefore you can run out of memory. In Camel 2.16.1/2.15.5 or older the default value is true. From newer versions the default value is false.</p></td></tr></tbody></table></div></div><p>You can append query options to the URI in the following format, <code>?option=value&option=value&...</code></p><p>Here is some examples on How to pass the parameters</p><p>For file (for webapp resources located in the Web Application directory --> cometd://localhost:8080?resourceBase=file./webapp<br clear="none"> For classpath (when by example the web resources are packaged inside the webapp folder --> cometd://localhost:8080?resourceBase=classpath:webapp</p><h3 id="BookInOnePage-Authentication">Authentication</h3><p><strong>Available as of Camel 2.8</strong></p><p>You can configure custom <code>SecurityPolicy</code> and <code>Extension</code>'s to the <cod
e>CometdComponent</code> which allows you to use authentication as <a shape="rect" class="external-link" href="http://cometd.org/documentation/howtos/authentication" rel="nofollow">documented here</a></p><h3 id="BookInOnePage-SettingupSSLforCometdComponent">Setting up SSL for Cometd Component</h3><h4 id="BookInOnePage-UsingtheJSSEConfigurationUtility">Using the JSSE Configuration Utility</h4><p>As of Camel 2.9, the Cometd component supports SSL/TLS configuration through the <a shape="rect" href="camel-configuration-utilities.html">Camel JSSE Configuration Utility</a>.  This utility greatly decreases the amount of component specific code you need to write and is configurable at the endpoint and component levels.  The following examples demonstrate how to use the utility with the Cometd component. You need to configure SSL on the CometdComponent.</p><h5 id="BookInOnePage-Programmaticconfigurationofthecomponent">Programmatic configuration of the component</h5><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[KeyStoreParameters ksp = new KeyStoreParameters();
ksp.setResource("/users/home/server/keystore.jks");
ksp.setPassword("keystorePassword");
@@ -17292,11 +17292,11 @@ template.send("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.rbtoc1452828120492 {padding: 0px;}
-div.rbtoc1452828120492 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1452828120492 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1452936175619 {padding: 0px;}
+div.rbtoc1452936175619 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1452936175619 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1452828120492">
+/*]]>*/</style></p><div class="toc-macro rbtoc1452936175619">
<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>
@@ -26761,53 +26761,18 @@ from("seda:someEndpoint").
</route>
]]></script>
</div></div><p></p><h3 id="BookInOnePage-SeeAlso.85">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="quartz.html">Quartz</a></li></ul> <h2 id="BookInOnePage-ValidationComponent">Validation Component</h2>
-
-<p>The Validation component performs XML validation of the message body using the JAXP Validation API and based on any of the supported XML schema languages, which defaults to <a shape="rect" class="external-link" href="http://www.w3.org/XML/Schema" rel="nofollow">XML Schema</a> </p>
-
-<p>Note that the <a shape="rect" href="jing.html">Jing</a> component also supports the following useful schema languages:</p>
-
-<ul><li><a shape="rect" class="external-link" href="http://relaxng.org/compact-tutorial-20030326.html" rel="nofollow">RelaxNG Compact Syntax</a></li><li><a shape="rect" class="external-link" href="http://relaxng.org/" rel="nofollow">RelaxNG XML Syntax</a></li></ul>
-
-
-<p>The <a shape="rect" href="msv.html">MSV</a> component also supports <a shape="rect" class="external-link" href="http://relaxng.org/" rel="nofollow">RelaxNG XML Syntax</a>.</p>
-
-<h3 id="BookInOnePage-URIformat.72">URI format</h3>
-
-<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[
-validator:someLocalOrRemoteResource
+<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="quartz.html">Quartz</a></li></ul> <h2 id="BookInOnePage-ValidationComponent">Validation Component</h2><p>The Validation component performs XML validation of the message body using the JAXP Validation API and based on any of the supported XML schema languages, which defaults to <a shape="rect" class="external-link" href="http://www.w3.org/XML/Schema" rel="nofollow">XML Schema</a></p><p>Note that the <a shape="rect" href="jing.html">Jing</a> component also supports the following useful schema languages:</p><ul><li><a shape="rect" class="external-link" href="http://relaxng.org/compact-tutorial-20030326.html" rel="nofollow">RelaxNG Compact Syntax</a></li><li><a shape="rect" class="extern
al-link" href="http://relaxng.org/" rel="nofollow">RelaxNG XML Syntax</a></li></ul><p>The <a shape="rect" href="msv.html">MSV</a> component also supports <a shape="rect" class="external-link" href="http://relaxng.org/" rel="nofollow">RelaxNG XML Syntax</a>.</p><h3 id="BookInOnePage-URIformat.72">URI format</h3><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[validator:someLocalOrRemoteResource
]]></script>
-</div></div>
-
-<p>Where <strong>someLocalOrRemoteResource</strong> is some URL to a local resource on the classpath or a full URL to a remote resource or resource on the file system which contains the XSD to validate against. For example:</p>
-
-<ul><li><code>msv:org/foo/bar.xsd</code></li><li><code>msv:file:../foo/bar.xsd</code></li><li><code>msv:<a shape="rect" class="external-link" href="http://acme.com/cheese.xsd" rel="nofollow">http://acme.com/cheese.xsd</a></code></li><li><code>validator:com/mypackage/myschema.xsd</code></li></ul>
-
-
-<p>Maven users will need to add the following dependency to their <code>pom.xml</code> for this component when using <strong>Camel 2.8</strong> or older:</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[
-<dependency>
+</div></div><p>Where <strong>someLocalOrRemoteResource</strong> is some URL to a local resource on the classpath or a full URL to a remote resource or resource on the file system which contains the XSD to validate against. For example:</p><ul><li><code>msv:org/foo/bar.xsd</code></li><li><code>msv:file:../foo/bar.xsd</code></li><li><code>msv:<a shape="rect" class="external-link" href="http://acme.com/cheese.xsd" rel="nofollow">http://acme.com/cheese.xsd</a></code></li><li><code>validator:com/mypackage/myschema.xsd</code></li></ul><p>Maven users will need to add the following dependency to their <code>pom.xml</code> for this component when using <strong>Camel 2.8</strong> or older:</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[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-spring</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
]]></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"><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"><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" rowsp
an="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" rowspa
n="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/ap
ache/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[
<route>
<from uri="direct:start"/>
@@ -26824,9 +26789,7 @@ validator:someLocalOrRemoteResource
</doTry>
</route>
]]></script>
-</div></div>
-
-<h3 id="BookInOnePage-SeeAlso.86">See Also</h3>
+</div></div><h3 id="BookInOnePage-Advanced:JMXmethodclearCachedSchema">Advanced: JMX method clearCachedSchema</h3><p>Since <strong>Camel 2.17</strong>, you can force that the cached schema in the validator endpoint is cleared and reread with the next process call with the JMX operation <code>clearCachedSchema. </code>You can also use this method to programmatically clear the cache. This method is available on the <code>ValidatorEndpoint </code>class<code>.</code></p><p></p><h3 id="BookInOnePage-SeeAlso.86">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> <h2 id="BookInOnePage-Velocity">Velocity</h2><p>The <strong>velocity:</strong> component allows you to process a message using an <a shape="rect" class="external-link" href="http://velocity.apache.org/">Apache Velocity</a> template. This can be ideal when using <a shape="rect" href="templating.html">Templating</a> to generate responses for requests.</p><p>Maven users will need to add the following dependency to their <code>pom.xml</code> for this component:</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[<dependency>
<groupId>org.apache.camel</groupId>
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.