Modified: websites/production/camel/content/validate.html
==============================================================================
--- websites/production/camel/content/validate.html (original)
+++ websites/production/camel/content/validate.html Thu Sep 14 19:25:46 2017
@@ -124,7 +124,7 @@ from("file://inbox")
 <h3 id="Validate-UsingfromSpringDSL">Using from Spring DSL</h3>
 <p>To use validate in the Spring DSL, the easiest way is to use <a 
shape="rect" class="external-link" 
href="http://camel.apache.org/simple.html";>simple</a> expressions.</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[
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[
 &lt;route&gt;
   &lt;from uri=&quot;file://inbox&quot;/&gt;
   &lt;validate&gt;
@@ -139,7 +139,7 @@ from(&quot;file://inbox&quot;)
 
 <p>The XML DSL to validate the message header would looks like this:</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[
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[
 &lt;route&gt;
   &lt;from uri=&quot;file://inbox&quot;/&gt;
   &lt;validate&gt;

Modified: websites/production/camel/content/vertx.html
==============================================================================
--- websites/production/camel/content/vertx.html (original)
+++ websites/production/camel/content/vertx.html Thu Sep 14 19:25:46 2017
@@ -86,7 +86,7 @@
         <tr>
         <td valign="top" width="100%">
 <div class="wiki-content maincontent"><h2 id="Vertx-VertxComponent">Vertx 
Component</h2><p><strong>Available as of Camel 2.12</strong></p><p>The 
<strong>vertx</strong> component is for working with the <a shape="rect" 
class="external-link" href="http://vertx.io/"; rel="nofollow">Vertx</a> <a 
shape="rect" class="external-link" 
href="http://vertx.io/core_manual_js.html#the-event-bus"; 
rel="nofollow">EventBus</a>.</p><p>The vertx <a shape="rect" 
class="external-link" href="http://vertx.io/core_manual_js.html#the-event-bus"; 
rel="nofollow">EventBus</a> sends and receives JSON events.</p><div 
class="confluence-information-macro 
confluence-information-macro-information"><span class="aui-icon aui-icon-small 
aui-iconfont-info confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><p>From <strong>Camel 2.16</strong> 
onwards vertx 3 is in use which requires Java 1.8 at 
runtime.</p></div></div><p>Maven users will need to add the following 
dependency to their <cod
 e>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[&lt;dependency&gt;
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[&lt;dependency&gt;
     &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
     &lt;artifactId&gt;camel-vertx&lt;/artifactId&gt;
     &lt;version&gt;x.x.x&lt;/version&gt;

Modified: websites/production/camel/content/virtualbox.html
==============================================================================
--- websites/production/camel/content/virtualbox.html (original)
+++ websites/production/camel/content/virtualbox.html Thu Sep 14 19:25:46 2017
@@ -137,7 +137,7 @@ from(&quot;direct:vboxCommands&quot;).
 
 <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[ 
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[ 
 &lt;dependency&gt; 
   &lt;groupId&gt;org.apache-extras.camel-extra&lt;/groupId&gt; 
   &lt;artifactId&gt;camel-virtualbox&lt;/artifactId&gt; 

Modified: websites/production/camel/content/vtd-xml.html
==============================================================================
--- websites/production/camel/content/vtd-xml.html (original)
+++ websites/production/camel/content/vtd-xml.html Thu Sep 14 19:25:46 2017
@@ -107,7 +107,7 @@ This component is particular efficient f
 
 <p>And in XML DSL</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[
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[
 &lt;route&gt;
    &lt;from uri=&quot;file:inbox&quot;/&gt;
    &lt;split streaming=&quot;true&quot;&gt;

Modified: websites/production/camel/content/walk-through-another-example.html
==============================================================================
--- websites/production/camel/content/walk-through-another-example.html 
(original)
+++ websites/production/camel/content/walk-through-another-example.html Thu Sep 
14 19:25:46 2017
@@ -98,7 +98,7 @@
 
 <p>This can be created in a route like this:</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[
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[
 &lt;route&gt;
    &lt;from uri=&quot;jms:queue:order&quot;/&gt;
    &lt;pipeline&gt;
@@ -113,7 +113,7 @@
 <div class="confluence-information-macro confluence-information-macro-tip"><p 
class="title">Pipeline is default</p><span class="aui-icon aui-icon-small 
aui-iconfont-approve confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body">
 <p>In the route above we specify <code>pipeline</code> but it can be omitted 
as its default, so you can write the route as:</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[
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[
 &lt;route&gt;
    &lt;from uri=&quot;jms:queue:order&quot;/&gt;
    &lt;bean ref=&quot;validateOrder&quot;/&gt;
@@ -126,7 +126,7 @@
 
 <p>An example where the pipeline needs to be used, is when using a multicast 
and "one" of the endpoints to send to (as a logical group) is a pipeline of 
other endpoints. For example.</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[
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[
 &lt;route&gt;
    &lt;from uri=&quot;jms:queue:order&quot;/&gt;
    &lt;multicast&gt;
@@ -143,7 +143,7 @@
 
 <p>The above sends the order (from <code>jms:queue:order</code>) to two 
locations at the same time, our log component, and to the "pipeline" of beans 
which goes one to the other. If you consider the opposite, sans the 
<code>&lt;pipeline&gt;</code></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[
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[
 &lt;route&gt;
    &lt;from uri=&quot;jms:queue:order&quot;/&gt;
    &lt;multicast&gt;
@@ -162,7 +162,7 @@
 <p>Where as the <code>bean ref</code> is a reference for a spring bean id, so 
we define our beans using regular Spring XML as:</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[
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[
    &lt;bean id=&quot;validateOrder&quot; 
class=&quot;com.mycompany.MyOrderValidator&quot;/&gt;
 ]]></script>
 </div></div>
@@ -178,7 +178,7 @@
 <p>In the route lets imagine that the registration of the order has to be done 
by sending data to a TCP socket that could be a big mainframe. As Camel has 
many <a shape="rect" href="components.html">Components</a> we will use the 
camel-mina component that supports <a shape="rect" href="mina.html">TCP</a> 
connectivity. So we change the route to:</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[
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[
 &lt;route&gt;
    &lt;from uri=&quot;jms:queue:order&quot;/&gt;
    &lt;bean ref=&quot;validateOrder&quot;/&gt;
@@ -195,7 +195,7 @@
 
 <p>What to notice here is that the <code>to</code> is not the end of the route 
(the world <img class="emoticon emoticon-wink" 
src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/wink.png";
 data-emoticon-name="wink" alt="(wink)">) in this example it's used in the 
middle of the <a shape="rect" href="pipes-and-filters.html">Pipes and 
filters</a>. In fact we can change the <code>bean</code> types to 
<code>to</code> as well:</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[
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[
 &lt;route&gt;
    &lt;from uri=&quot;jms:queue:order&quot;/&gt;
    &lt;to uri=&quot;bean:validateOrder&quot;/&gt;

Modified: websites/production/camel/content/weather.html
==============================================================================
--- websites/production/camel/content/weather.html (original)
+++ websites/production/camel/content/weather.html Thu Sep 14 19:25:46 2017
@@ -86,7 +86,7 @@
         <tr>
         <td valign="top" width="100%">
 <div class="wiki-content maincontent"><h2 
id="Weather-WeatherComponent">Weather Component</h2><p><strong>Available as of 
Camel 2.12</strong></p><p>The <strong>weather:</strong> component is used for 
polling weather information from <a shape="rect" class="external-link" 
href="http://openweathermap.org"; rel="nofollow">Open Weather Map</a> - a site 
that provides free global weather and forecast information. The information is 
returned as a json String object.</p><p>Camel will poll for updates to the 
current weather and forecasts once per hour by default. It can also be used to 
query the weather api based on the parameters defined on the endpoint which is 
used as producer.</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[&lt;dependency&gt;
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[&lt;dependency&gt;
     &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
     &lt;artifactId&gt;camel-weather&lt;/artifactId&gt;
     &lt;version&gt;x.x.x&lt;/version&gt;

Modified: 
websites/production/camel/content/why-does-camel-use-too-many-threads-with-producertemplate.html
==============================================================================
--- 
websites/production/camel/content/why-does-camel-use-too-many-threads-with-producertemplate.html
 (original)
+++ 
websites/production/camel/content/why-does-camel-use-too-many-threads-with-producertemplate.html
 Thu Sep 14 19:25:46 2017
@@ -97,7 +97,7 @@
 <p>For instance using <a shape="rect" href="spring.html">Spring</a> you can 
define a template and have Spring handle the lifecycle of it:</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[
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[
     &lt;camelContext 
xmlns=&quot;http://activemq.apache.org/camel/schema/spring&quot;&gt;
         &lt;template id=&quot;template&quot;/&gt;
     &lt;/camelContext&gt;

Modified: websites/production/camel/content/xml-security-component.html
==============================================================================
--- websites/production/camel/content/xml-security-component.html (original)
+++ websites/production/camel/content/xml-security-component.html Thu Sep 14 
19:25:46 2017
@@ -86,7 +86,7 @@
         <tr>
         <td valign="top" width="100%">
 <div class="wiki-content maincontent"><h2 
id="XMLSecuritycomponent-XMLSecuritycomponent">XML Security 
component</h2><p><strong>Available as of Camel 2.12.0</strong></p><p>With this 
Apache Camel component, you can generate and validate XML signatures as 
described in the W3C standard <a shape="rect" class="external-link" 
href="http://www.w3.org/TR/xmldsig-core/"; rel="nofollow">XML Signature Syntax 
and Processing</a> or as described in the successor <a shape="rect" 
class="external-link" href="http://www.w3.org/TR/xmldsig-core1/"; 
rel="nofollow">version 1.1</a>. For XML Encryption support, please refer to the 
XML Security <a shape="rect" href="data-format.html">Data Format</a>.</p><p>You 
can find an introduction to XML signature <a shape="rect" class="external-link" 
href="http://www.oracle.com/technetwork/articles/javase/dig-signatures-141823.html";
 rel="nofollow">here</a>. The implementation of the component is based on <a 
shape="rect" class="external-link" href="http://docs.oracle.com/j
 avase/6/docs/technotes/guides/security/xmldsig/overview.html" 
rel="nofollow">JSR 105</a>, the Java API corresponding to the W3C standard and 
supports the Apache Santuario and the JDK provider for JSR 105. The 
implementation will first try to use the Apache Santuario provider; if it does 
not find the Santuario provider, it will use the JDK provider. Further, the 
implementation is DOM based.</p><p>Since Camel 2.15.0 we also provide support 
for <strong>XAdES-BES/EPES</strong> for the signer endpoint; see subsection 
"XAdES-BES/EPES for the Signer Endpoint".</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[&lt;dependency&gt;
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[&lt;dependency&gt;
     &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
     &lt;artifactId&gt;camel-xmlsecurity&lt;/artifactId&gt;
     &lt;version&gt;x.x.x&lt;/version&gt;

Modified: websites/production/camel/content/xmlbeans.html
==============================================================================
--- websites/production/camel/content/xmlbeans.html (original)
+++ websites/production/camel/content/xmlbeans.html Thu Sep 14 19:25:46 2017
@@ -104,7 +104,7 @@ from(&quot;activemq:My.Queue&quot;).
 <p>If you use maven you could just add the following to your pom.xml, 
substituting the version number for the latest &amp; greatest release (see <a 
shape="rect" href="download.html">the download page for the latest 
versions</a>).</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[
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[
 &lt;dependency&gt;
   &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
   &lt;artifactId&gt;camel-xmlbeans&lt;/artifactId&gt;

Modified: websites/production/camel/content/xmljson.html
==============================================================================
--- websites/production/camel/content/xmljson.html (original)
+++ websites/production/camel/content/xmljson.html Thu Sep 14 19:25:46 2017
@@ -195,7 +195,7 @@ namespacesFormat.setRootElement(&quot;pe
 &lt;/person&gt;
 ]]></script>
 </div></div><p>Remember that the JSON spec defines a JSON object as 
follows:</p><blockquote><p>An object is an unordered set of name/value pairs. 
[...].</p></blockquote><p>That's why the elements are in a different order in 
the output XML.</p><h3 id="XmlJson-Dependencies">Dependencies</h3><p>To use the 
<a shape="rect" href="xmljson.html">XmlJson</a> dataformat in your camel routes 
you need to add the following dependency to your pom.</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;dependency&gt;
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[&lt;dependency&gt;
   &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
   &lt;artifactId&gt;camel-xmljson&lt;/artifactId&gt;
   &lt;version&gt;x.x.x&lt;/version&gt;

Modified: websites/production/camel/content/xmlsecurity-dataformat.html
==============================================================================
--- websites/production/camel/content/xmlsecurity-dataformat.html (original)
+++ websites/production/camel/content/xmlsecurity-dataformat.html Thu Sep 14 
19:25:46 2017
@@ -149,7 +149,7 @@ context.addRoutes(new RouteBuilder() {
 }
 ]]></script>
 </div></div><h5 id="XMLSecurityDataFormat-SpringXML">Spring XML</h5><p>A 
namespace prefix that is defined as part of the <code>camelContext</code> 
definition can be re-used in context within the data format 
<code>secureTag</code> attribute of the <code>secureXML</code> element.</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;camelContext 
id=&quot;springXmlSecurityDataFormatTestCamelContext&quot; 
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[&lt;camelContext 
id=&quot;springXmlSecurityDataFormatTestCamelContext&quot; 
               xmlns=&quot;http://camel.apache.org/schema/spring&quot;
               
xmlns:cheese=&quot;http://cheese.xmlsecurity.camel.apache.org/&quot;&gt;        
     &lt;route&gt;
@@ -161,7 +161,7 @@ context.addRoutes(new RouteBuilder() {
             ...
 ]]></script>
 </div></div><h4 id="XMLSecurityDataFormat-AsymmetricKeyEncryption">Asymmetric 
Key Encryption</h4><h5 id="XMLSecurityDataFormat-SpringXMLSender">Spring XML 
Sender</h5><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;!--  trust store configuration --&gt;     
                     
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[&lt;!--  trust store configuration --&gt;     
                     
 &lt;camel:keyStoreParameters id=&quot;trustStoreParams&quot; 
resource=&quot;./sender.ts&quot; password=&quot;password&quot;/&gt;
 
 &lt;camelContext id=&quot;springXmlSecurityDataFormatTestCamelContext&quot; 
@@ -180,7 +180,7 @@ context.addRoutes(new RouteBuilder() {
             ...
 ]]></script>
 </div></div><h5 id="XMLSecurityDataFormat-SpringXMLRecipient">Spring XML 
Recipient</h5><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[ 
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[ 
 &lt;!--  key store configuration --&gt;
 &lt;camel:keyStoreParameters id=&quot;keyStoreParams&quot; 
resource=&quot;./recipient.ks&quot; password=&quot;password&quot; /&gt;
 

Modified: websites/production/camel/content/xmpp.html
==============================================================================
--- websites/production/camel/content/xmpp.html (original)
+++ websites/production/camel/content/xmpp.html Thu Sep 14 19:25:46 2017
@@ -87,7 +87,7 @@
         <tr>
         <td valign="top" width="100%">
 <div class="wiki-content maincontent"><h2 id="XMPP-XMPPComponent">XMPP 
Component</h2><p>The <strong>xmpp:</strong> component implements an XMPP 
(Jabber) transport.</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[&lt;dependency&gt;
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[&lt;dependency&gt;
     &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
     &lt;artifactId&gt;camel-xmpp&lt;/artifactId&gt;
     &lt;version&gt;x.x.x&lt;/version&gt;

Modified: websites/production/camel/content/xquery-endpoint.html
==============================================================================
--- websites/production/camel/content/xquery-endpoint.html (original)
+++ websites/production/camel/content/xquery-endpoint.html Thu Sep 14 19:25:46 
2017
@@ -91,7 +91,7 @@
 
 <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[
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[
 &lt;dependency&gt;
     &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
     &lt;artifactId&gt;camel-saxon&lt;/artifactId&gt;

Modified: websites/production/camel/content/xslt.html
==============================================================================
--- websites/production/camel/content/xslt.html (original)
+++ websites/production/camel/content/xslt.html Thu Sep 14 19:25:46 2017
@@ -98,7 +98,7 @@
 
 
 <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[&lt;dependency&gt;
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[&lt;dependency&gt;
     &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
     &lt;artifactId&gt;camel-spring&lt;/artifactId&gt;
     &lt;version&gt;x.x.x&lt;/version&gt;
@@ -118,18 +118,18 @@
   to(&quot;activemq:Another.Queue&quot;);
 ]]></script>
 </div></div><h3 id="XSLT-GettingParametersintotheXSLTtoworkwith">Getting 
Parameters into the XSLT to work with</h3><p>By default, all headers are added 
as parameters which are available in the XSLT.<br clear="none"> To do this you 
will need to declare the parameter so it is then <em>useable</em>.</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;setHeader 
headerName=&quot;myParam&quot;&gt;&lt;constant&gt;42&lt;/constant&gt;&lt;/setHeader&gt;
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[&lt;setHeader 
headerName=&quot;myParam&quot;&gt;&lt;constant&gt;42&lt;/constant&gt;&lt;/setHeader&gt;
 &lt;to uri=&quot;xslt:MyTransform.xsl&quot;/&gt;
 ]]></script>
 </div></div><p>And the XSLT just needs to declare it at the top level for it 
to be available:</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;xsl: ...... &gt;
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[&lt;xsl: ...... &gt;
 
    &lt;xsl:param name=&quot;myParam&quot;/&gt;
   
     &lt;xsl:template ...&gt;
 ]]></script>
 </div></div><h3 id="XSLT-SpringXMLversions">Spring XML versions</h3><p>To use 
the above examples in Spring XML you would use something like</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;camelContext 
xmlns=&quot;http://activemq.apache.org/camel/schema/spring&quot;&gt;
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[  &lt;camelContext 
xmlns=&quot;http://activemq.apache.org/camel/schema/spring&quot;&gt;
     &lt;route&gt;
       &lt;from uri=&quot;activemq:My.Queue&quot;/&gt;
       &lt;to 
uri=&quot;xslt:org/apache/camel/spring/processor/example.xsl&quot;/&gt;
@@ -138,10 +138,10 @@
   &lt;/camelContext&gt;
 ]]></script>
 </div></div><p>There is a <a shape="rect" class="external-link" 
href="http://svn.apache.org/repos/asf/camel/trunk/components/camel-spring/src/test/java/org/apache/camel/spring/processor/XsltTest.java";>test
 case</a> along with <a shape="rect" class="external-link" 
href="http://svn.apache.org/repos/asf/camel/trunk/components/camel-spring/src/test/resources/org/apache/camel/spring/processor/XsltTest-context.xml";>its
 Spring XML</a> if you want a concrete example.</p><h3 
id="XSLT-Usingxsl:include">Using xsl:include</h3><p><strong>Camel 2.2 or 
older</strong><br clear="none"> If you use xsl:include in your XSL files then 
in Camel 2.2 or older it uses the default 
<code>javax.xml.transform.URIResolver</code> which means it can only lookup 
files from file system, and its does that relative from the JVM starting 
folder.</p><p>For example this include:</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;xsl:include 
href=&quot;staff_template.xsl&quot;/&gt;
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[&lt;xsl:include 
href=&quot;staff_template.xsl&quot;/&gt;
 ]]></script>
 </div></div><p>Will lookup the <code>staff_tempkalte.xsl</code> file from the 
starting folder where the application was started.</p><p><strong>Camel 2.3 or 
newer</strong> <br clear="none"> Now Camel provides its own implementation of 
<code>URIResolver</code> which allows Camel to load included files from the 
classpath and more intelligent than before.</p><p>For example this 
include:</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;xsl:include 
href=&quot;staff_template.xsl&quot;/&gt;
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[&lt;xsl:include 
href=&quot;staff_template.xsl&quot;/&gt;
 ]]></script>
 </div></div><p>Will now be located relative from the starting endpoint, which 
for example could be:</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[.to(&quot;xslt:org/apache/camel/component/xslt/staff_include_relative.xsl&quot;)
@@ -150,16 +150,16 @@
 <script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[    &lt;xsl:include 
href=&quot;../staff_other_template.xsl&quot;/&gt;
 ]]></script>
 </div></div><p>Which then will resolve the xsl file under 
<code>org/apache/camel/component</code>.</p><h4 
id="XSLT-Usingxsl:includeanddefaultprefix">Using xsl:include and default 
prefix</h4><p>When using xsl:include such as:</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;xsl:include 
href=&quot;staff_template.xsl&quot;/&gt;
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[&lt;xsl:include 
href=&quot;staff_template.xsl&quot;/&gt;
 ]]></script>
 </div></div><p>Then in Camel 2.10.3 and older, then Camel will use 
"classpath:" as the default prefix, and load the resource from the classpath. 
This works for most cases, but if you configure the starting resource to load 
from file,</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[.to(&quot;xslt:file:etc/xslt/staff_include_relative.xsl&quot;)
 ]]></script>
 </div></div><p>.. then you would have to prefix all your includes with "file:" 
as well.</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;xsl:include 
href=&quot;file:staff_template.xsl&quot;/&gt;
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[&lt;xsl:include 
href=&quot;file:staff_template.xsl&quot;/&gt;
 ]]></script>
 </div></div><p>From Camel 2.10.4 onwards we have made this easier as Camel 
will use the prefix from the endpoint configuration as the default prefix. So 
from Camel 2.10.4 onwards you can do:</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;xsl:include 
href=&quot;staff_template.xsl&quot;/&gt;
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[&lt;xsl:include 
href=&quot;staff_template.xsl&quot;/&gt;
 ]]></script>
 </div></div><p>Which will load the staff_template.xsl resource from the file 
system, as the endpoint was configured with "file:" as prefix.<br clear="none"> 
You can still though explicit configure a prefix, and then mix and match. And 
have both file and classpath loading. But that would be unusual, as most people 
either use file or classpath based resources.</p><h3 
id="XSLT-UsingSaxonextensionfunctions">Using Saxon extension 
functions</h3><p>Since Saxon 9.2, writing extension functions has been 
supplemented by a new mechanism, referred to as&#160;<a shape="rect" 
class="external-link" 
href="http://www.saxonica.com/html/documentation/extensibility/integratedfunctions";
 rel="nofollow" title="Follow link">integrated extension functions</a>&#160;you 
can now easily use camel:</p><div><p>&#160;</p><p>-&#160;Java example:</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[SimpleRegistry registry = new 
SimpleRegistry();

Modified: websites/production/camel/content/yammer.html
==============================================================================
--- websites/production/camel/content/yammer.html (original)
+++ websites/production/camel/content/yammer.html Thu Sep 14 19:25:46 2017
@@ -86,7 +86,7 @@
         <tr>
         <td valign="top" width="100%">
 <div class="wiki-content maincontent"><h2 
id="Yammer-Yammer">Yammer</h2><p><strong>Available as of Camel 
2.12</strong></p><p>The Yammer component allows you to interact with the <a 
shape="rect" class="external-link" href="https://www.yammer.com"; 
rel="nofollow">Yammer</a> enterprise social network. Consuming messages, users, 
and user relationships is supported as well as creating new 
messages.</p><p>Yammer uses OAuth 2 for all client application authentication. 
In order to use camel-yammer with your account, you'll need to create a new 
application within Yammer and grant the application access to your account. 
Finally, generate your access token. More details are at <a shape="rect" 
class="external-link" 
href="https://developer.yammer.com/v1.0/docs/authentication"; 
rel="nofollow">https://developer.yammer.com/v1.0/docs/authentication</a></p><p>Maven
 users will need to add the following dependency to their pom.xml for this 
component:</p><div class="code panel pdl" style="border-width: 1p
 x;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[&lt;dependency&gt;
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[&lt;dependency&gt;
     &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
     &lt;artifactId&gt;camel-yammer&lt;/artifactId&gt;
     &lt;version&gt;${camel-version}&lt;/version&gt;

Modified: websites/production/camel/content/zeromq.html
==============================================================================
--- websites/production/camel/content/zeromq.html (original)
+++ websites/production/camel/content/zeromq.html Thu Sep 14 19:25:46 2017
@@ -86,7 +86,7 @@
         <tr>
         <td valign="top" width="100%">
 <div class="wiki-content maincontent"><h2 
id="ZeroMQ-CamelZeroMQComponent">Camel ZeroMQ 
Component</h2><p><strong>Available as of Camel 2.11</strong></p><p>The 
<strong>camel-zeromq</strong> component is provided by the <a shape="rect" 
class="external-link" href="http://code.google.com/p/camel-extra/"; 
rel="nofollow">Camel Extra</a> project which hosts *GPL related components for 
Camel.</p><p>The <strong>camel-zeromq</strong> component allows you to consumer 
or produce messages using <a shape="rect" class="external-link" 
href="http://zeromq.org/"; rel="nofollow">ZeroMQ</a>. Zeromq requires a bit of 
work to get setup, especially on windows. Refer to <a shape="rect" 
class="external-link" href="http://www.zeromq.org/intro:get-the-software"; 
rel="nofollow">the documentation</a>. Note: This component works with the 
stable 2.2 branch and not the pre-release 3.2.</p><p>This component uses Akka 
for it's Zeromq "driver" but does not use Scala Actors. This means the 
component does not require the 
 JZMQ libraries to be built and present, just the native ZeroMQ library that is 
installed when you build ZeroMQ on your system. There is some discussion as to 
the speed of the Akka driver, and so it is possible to switch to using the JZMQ 
driver if you wish. Simply remove the Akka Zeromq dependancy and replace it 
with the JZMQ jar and ensure the zmq.lib is present on your system. For more 
information see <a shape="rect" class="external-link" 
href="http://www.zeromq.org/bindings:java"; rel="nofollow">here</a>.</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[&lt;dependency&gt;
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[&lt;dependency&gt;
     &lt;groupId&gt;org.apache-extras.camel-extra&lt;/groupId&gt;
     &lt;artifactId&gt;camel-zeromq&lt;/artifactId&gt;
     &lt;version&gt;x.x.x&lt;/version&gt;

Modified: websites/production/camel/content/zip-file-dataformat.html
==============================================================================
--- websites/production/camel/content/zip-file-dataformat.html (original)
+++ websites/production/camel/content/zip-file-dataformat.html Thu Sep 14 
19:25:46 2017
@@ -127,7 +127,7 @@
      .setHeader(Exchange.FILE_NAME, constant(&quot;reports.zip&quot;))
    .to(&quot;file:output/directory&quot;);]]></script>
 </div></div><p>&#160;</p></div><h3 
id="ZipFileDataFormat-Dependencies">Dependencies</h3><p>To use Zip files in 
your camel routes you need to add a dependency on 
<strong>camel-zipfile</strong> which implements this data format.</p><p>If you 
use Maven you can just add the following to your <code>pom.xml</code>, 
substituting the version number for the latest &amp; greatest release (see <a 
shape="rect" href="download.html">the download page for the latest 
versions</a>).</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;dependency&gt;
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[&lt;dependency&gt;
   &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
   &lt;artifactId&gt;camel-zipfile&lt;/artifactId&gt;
   &lt;version&gt;x.x.x&lt;/version&gt;

Modified: websites/production/camel/content/zookeeper.html
==============================================================================
--- websites/production/camel/content/zookeeper.html (original)
+++ websites/production/camel/content/zookeeper.html Thu Sep 14 19:25:46 2017
@@ -86,7 +86,7 @@
         <tr>
         <td valign="top" width="100%">
 <div class="wiki-content maincontent"><h2 
id="Zookeeper-ZooKeeper">ZooKeeper</h2><p><strong>Available as of Camel 
2.9</strong></p><p>The ZooKeeper component allows interaction with a <a 
shape="rect" class="external-link" 
href="http://hadoop.apache.org/zookeeper/";>ZooKeeper</a> cluster and exposes 
the following features to Camel:</p><ol><li>Creation of nodes in any of the 
ZooKeeper create modes.</li><li>Get and Set the data contents of arbitrary 
cluster nodes. (data being set must be convertable to byte[])</li><li>Create 
and retrieve the list the child nodes attached to a particular node.</li><li>A 
Distributed <a shape="rect" href="routepolicy.html">RoutePolicy</a> that 
leverages a Leader election coordinated by ZooKeeper to determine if exchanges 
should get processed.</li></ol><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[&lt;dependency&gt;
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[&lt;dependency&gt;
     &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
     &lt;artifactId&gt;camel-zookeeper&lt;/artifactId&gt;
     &lt;version&gt;x.x.x&lt;/version&gt;
@@ -119,7 +119,7 @@ template.sendBodyAndHeader(&quot;direct:
 <script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[from(&quot;direct:delete-znode&quot;).setHeader(ZooKeeperMessage.ZOOKEEPER_OPERATION,
 
constant(&quot;DELETE&quot;)).to(&quot;zookeeper://localhost:39913/somepath/somenode&quot;);
 ]]></script>
 </div></div><p>or equivalently</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;
+<script class="brush: java; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[&lt;route&gt;
   &lt;from uri=&quot;direct:delete-znode&quot; /&gt;
   &lt;setHeader headerName=&quot;CamelZookeeperOperation&quot;&gt;
      &lt;constant&gt;DELETE&lt;/constant&gt;


Reply via email to