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 2018/05/21 05:25:24 UTC

svn commit: r1030133 [8/14] - in /websites/production/camel/content: ./ cache/

Modified: websites/production/camel/content/how-do-i-retrieve-the-thrown-exception-during-processing-an-exchange.html
==============================================================================
--- websites/production/camel/content/how-do-i-retrieve-the-thrown-exception-during-processing-an-exchange.html (original)
+++ websites/production/camel/content/how-do-i-retrieve-the-thrown-exception-during-processing-an-exchange.html Mon May 21 05:25:23 2018
@@ -97,43 +97,41 @@
 
 <p>From the returned Exchange you can test if its failed and get the caused exception. This is illustrated in the code sample:</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[
+Error rendering macro 'code': Invalid value specified for parameter 'java.lang.NullPointerException'<pre class="conf-macro output-inline" data-hasbody="true" data-macro-name="unmigrated-inline-wiki-markup">
 public void testBeanInvocation() {
-    int result = (Integer) template.sendBody(&quot;direct:input&quot;, ExchangePattern.InOut, &quot;Hello London&quot;);
+    int result = (Integer) template.sendBody("direct:input", ExchangePattern.InOut, "Hello London");
     assertEquals(1, result);
 }
 
 public void testBeanInvocationFailure() {
     // must create an exchange to get the result as an exchange where we can get the caused exception
-    Exchange exchange = getMandatoryEndpoint(&quot;direct:input&quot;).createExchange(ExchangePattern.InOut);
-    exchange.getIn().setBody(&quot;Hello Paris&quot;);
+    Exchange exchange = getMandatoryEndpoint("direct:input").createExchange(ExchangePattern.InOut);
+    exchange.getIn().setBody("Hello Paris");
 
-    Exchange out = template.send(&quot;direct:input&quot;, exchange);
-    assertTrue(&quot;Should be failed&quot;, out.isFailed());
-    assertTrue(&quot;Should be IllegalArgumentException&quot;, out.getException() instanceof IllegalArgumentException);
-    assertEquals(&quot;Forced exception&quot;, out.getException().getMessage());
+    Exchange out = template.send("direct:input", exchange);
+    assertTrue("Should be failed", out.isFailed());
+    assertTrue("Should be IllegalArgumentException", out.getException() instanceof IllegalArgumentException);
+    assertEquals("Forced exception", out.getException().getMessage());
 }
 
 protected RouteBuilder createRouteBuilder() throws Exception {
     return new RouteBuilder() {
         public void configure() throws Exception {
-            from(&quot;direct:input&quot;).bean(new ExceptionBean());
+            from("direct:input").bean(new ExceptionBean());
         }
     };
 }
 
 public static class ExceptionBean {
     public int doSomething(String request) throws Exception {
-        if (request.equals(&quot;Hello London&quot;)) {
+        if (request.equals("Hello London")) {
             return 1;
         } else {
-            throw new IllegalArgumentException(&quot;Forced exception&quot;);
+            throw new IllegalArgumentException("Forced exception");
         }
     }
 }
-]]></script>
-</div></div></div>
+</pre></div>
         </td>
         <td valign="top">
           <div class="navigation">

Modified: websites/production/camel/content/how-do-i-retry-processing-a-message-from-a-certain-point-back-or-an-entire-route.html
==============================================================================
--- websites/production/camel/content/how-do-i-retry-processing-a-message-from-a-certain-point-back-or-an-entire-route.html (original)
+++ websites/production/camel/content/how-do-i-retry-processing-a-message-from-a-certain-point-back-or-an-entire-route.html Mon May 21 05:25:23 2018
@@ -95,33 +95,30 @@
 
 <p>In the example above we have 2 routes (direct:start, direct:sub). In case of a failure anywhere in the direct:sub route, then the entire route is retried. This happens because we have instructed the direct:sub route to not use any error handler (eg the no error handler). Then we link the routes using the <a shape="rect" href="direct.html">Direct</a> component by calling the sub route from the 1st route.</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[
+Error rendering macro 'code': Invalid value specified for parameter 'java.lang.NullPointerException'<pre class="conf-macro output-inline" data-hasbody="true" data-macro-name="unmigrated-inline-wiki-markup">
 
 // in case of io exception then try to redeliver up till 2 times
 // (do not use any delay due faster unit testing)
 onException(IOException.class)
     .maximumRedeliveries(2).redeliveryDelay(0);
 
-from(&quot;direct:start&quot;)
-    .to(&quot;mock:a&quot;)
+from("direct:start")
+    .to("mock:a")
     // call sub route (using direct)
-    .to(&quot;direct:sub&quot;)
-    .to(&quot;mock:c&quot;);
+    .to("direct:sub")
+    .to("mock:c");
 
-from(&quot;direct:sub&quot;)
+from("direct:sub")
     // disable error handler, so the entire route can be retried in case of redelivery
     .errorHandler(noErrorHandler())
-    .to(&quot;mock:b&quot;)
+    .to("mock:b")
     .process(new MyProcessor());
-]]></script>
-</div></div>
+</pre>
 
 <p>The code above is based on an unit test, and as you can see the processor below is configured to fail the first 2 attempts. <br clear="none">
 So that means the entire direct:sub route is redeliveried, meaning that the "mock:b" endpoint receives the incoming message again.</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[
+Error rendering macro 'code': Invalid value specified for parameter 'java.lang.NullPointerException'<pre class="conf-macro output-inline" data-hasbody="true" data-macro-name="unmigrated-inline-wiki-markup">
 public static class MyProcessor implements Processor {
 
     private int counter;
@@ -130,51 +127,48 @@ public static class MyProcessor implemen
     public void process(Exchange exchange) throws Exception {
         // use a processor to simulate error in the first 2 calls
         if (counter++ &lt; 2) {
-            throw new IOException(&quot;Forced&quot;);
+            throw new IOException("Forced");
         }
-        exchange.getIn().setBody(&quot;Bye World&quot;);
+        exchange.getIn().setBody("Bye World");
     }
 }
-]]></script>
-</div></div>
+</pre>
 
 <p>The same example is shown below using the 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[
+Error rendering macro 'code': Invalid value specified for parameter 'java.lang.NullPointerException'<pre class="conf-macro output-inline" data-hasbody="true" data-macro-name="unmigrated-inline-wiki-markup">
 &lt;!-- this is the processor that will fail the first 2 attempts --&gt;
-&lt;bean id=&quot;myProcessor&quot; class=&quot;org.apache.camel.processor.RedeliverToSubRouteTest.MyProcessor&quot;/&gt;
+&lt;bean id="myProcessor" class="org.apache.camel.processor.RedeliverToSubRouteTest.MyProcessor"/&gt;
 
-&lt;camelContext xmlns=&quot;http://camel.apache.org/schema/spring&quot;&gt;
+&lt;camelContext xmlns="http://camel.apache.org/schema/spring"&gt;
 
 	&lt;!-- setup no error handler with an id, we refer to from the 2nd route --&gt;
-	&lt;errorHandler id=&quot;noErrorHandler&quot; type=&quot;NoErrorHandler&quot;/&gt;
+	&lt;errorHandler id="noErrorHandler" type="NoErrorHandler"/&gt;
 
 	&lt;!-- configure on exception to redelivery at most 2 times when an IOException was thrown
 	     do not use redelivery delay to run unit test faster --&gt;
 	&lt;onException&gt;
 		&lt;exception&gt;java.io.IOException&lt;/exception&gt;
-		&lt;redeliveryPolicy maximumRedeliveries=&quot;2&quot; redeliveryDelay=&quot;0&quot;/&gt;
+		&lt;redeliveryPolicy maximumRedeliveries="2" redeliveryDelay="0"/&gt;
 	&lt;/onException&gt;
 
 	&lt;!-- 1st route, no need to setup error handler, as it will use the default error handler --&gt;
 	&lt;route&gt;
-		&lt;from uri=&quot;direct:start&quot;/&gt;
-		&lt;to uri=&quot;mock:a&quot;/&gt;
-		&lt;to uri=&quot;direct:sub&quot;/&gt;
-		&lt;to uri=&quot;mock:c&quot;/&gt;
+		&lt;from uri="direct:start"/&gt;
+		&lt;to uri="mock:a"/&gt;
+		&lt;to uri="direct:sub"/&gt;
+		&lt;to uri="mock:c"/&gt;
 	&lt;/route&gt;
 
 	&lt;!-- disable error handler on this route, so the entire route can be redelivered
 	     when called from the 1st route --&gt;
-	&lt;route errorHandlerRef=&quot;noErrorHandler&quot;&gt;
-		&lt;from uri=&quot;direct:sub&quot;/&gt;
-		&lt;to uri=&quot;mock:b&quot;/&gt;
-		&lt;process ref=&quot;myProcessor&quot;/&gt;
+	&lt;route errorHandlerRef="noErrorHandler"&gt;
+		&lt;from uri="direct:sub"/&gt;
+		&lt;to uri="mock:b"/&gt;
+		&lt;process ref="myProcessor"/&gt;
 	&lt;/route&gt;
 &lt;/camelContext&gt;
-]]></script>
-</div></div></div>
+</pre></div>
         </td>
         <td valign="top">
           <div class="navigation">

Modified: websites/production/camel/content/jackson-xml.html
==============================================================================
--- websites/production/camel/content/jackson-xml.html (original)
+++ websites/production/camel/content/jackson-xml.html Mon May 21 05:25:23 2018
@@ -89,27 +89,26 @@
 	<tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="JacksonXML-JacksonXML">Jackson XML</h2><p><strong>Available as of Camel 2.16</strong></p><p>Jackson XML is a <a shape="rect" href="data-format.html">Data Format</a> which uses the <a shape="rect" class="external-link" href="http://wiki.fasterxml.com/JacksonHome/" rel="nofollow">Jackson library</a>&#160;with the <a shape="rect" class="external-link" href="https://github.com/FasterXML/jackson-dataformat-xml" rel="nofollow">XMLMapper extension</a> to unmarshal an XML payload into Java objects or to marshal Java objects into an XML payload.</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>If you are familiar with Jackson, this XML data format behaves in the same way as its JSON counterpart, and thus can be used with classes annotated for JSON serialization/dese
 rialization.</p><p>This extension also mimics <a shape="rect" class="external-link" href="https://github.com/FasterXML/jackson-dataformat-xml/blob/master/README.md" rel="nofollow">JAXB's "Code first" approach</a>.</p><p>This data format relies on <a shape="rect" class="external-link" href="http://wiki.fasterxml.com/WoodstoxHome" rel="nofollow">Woodstox</a> (especially for features like pretty printing), a fast and efficient XML processor.</p></div></div><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[from(&quot;activemq:My.Queue&quot;).
+<div class="wiki-content maincontent"><h2 id="JacksonXML-JacksonXML">Jackson XML</h2><p><strong>Available as of Camel 2.16</strong></p><p>Jackson XML is a <a shape="rect" href="data-format.html">Data Format</a> which uses the <a shape="rect" class="external-link" href="http://wiki.fasterxml.com/JacksonHome/" rel="nofollow">Jackson library</a>&#160;with the <a shape="rect" class="external-link" href="https://github.com/FasterXML/jackson-dataformat-xml" rel="nofollow">XMLMapper extension</a> to unmarshal an XML payload into Java objects or to marshal Java objects into an XML payload.</p><div class="confluence-information-macro confluence-information-macro-information conf-macro output-block" data-hasbody="true" data-macro-name="info"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"> </span><div class="confluence-information-macro-body"><p>If you are familiar with Jackson, this XML data format behaves in the same way as its JSON counterpart, and
  thus can be used with classes annotated for JSON serialization/deserialization.</p><p>This extension also mimics <a shape="rect" class="external-link" href="https://github.com/FasterXML/jackson-dataformat-xml/blob/master/README.md" rel="nofollow">JAXB's "Code first" approach</a>.</p><p>This data format relies on <a shape="rect" class="external-link" href="http://wiki.fasterxml.com/WoodstoxHome" rel="nofollow">Woodstox</a> (especially for features like pretty printing), a fast and efficient XML processor.</p></div></div><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">from("activemq:My.Queue").
   unmarshal().jacksonxml().
-  to(&quot;mqseries:Another.Queue&quot;);
-]]></script>
-</div></div><h4 id="JacksonXML-UsingJacksonXMLinSpringDSL">Using Jackson XML in Spring DSL</h4><p>When using&#160;<a shape="rect" href="data-format.html">Data Format</a>&#160;in Spring DSL you need to declare the data formats first. This is done in the&#160;<strong>DataFormats</strong>&#160;XML tag.</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;dataFormats&gt;
+  to("mqseries:Another.Queue");
+</pre>
+</div></div><h4 id="JacksonXML-UsingJacksonXMLinSpringDSL">Using Jackson XML in Spring DSL</h4><p>When using&#160;<a shape="rect" href="data-format.html">Data Format</a>&#160;in Spring DSL you need to declare the data formats first. This is done in the&#160;<strong>DataFormats</strong>&#160;XML tag.</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: xml; gutter: false; theme: Default" data-theme="Default">        &lt;dataFormats&gt;
             &lt;!-- here we define a Xml data format with the id jack and that it should use the TestPojo as the class type when
                  doing unmarshal. The unmarshalTypeName is optional, if not provided Camel will use a Map as the type --&gt;
-            &lt;jacksonxml id=&quot;jack&quot; unmarshalTypeName=&quot;org.apache.camel.component.jacksonxml.TestPojo&quot;/&gt;
+            &lt;jacksonxml id="jack" unmarshalTypeName="org.apache.camel.component.jacksonxml.TestPojo"/&gt;
         &lt;/dataFormats&gt;
-]]></script>
-</div></div><p>And then you can refer to this id in the route:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[       &lt;route&gt;
-            &lt;from uri=&quot;direct:back&quot;/&gt;
-            &lt;unmarshal ref=&quot;jack&quot;/&gt;
-            &lt;to uri=&quot;mock:reverse&quot;/&gt;
+</pre>
+</div></div><p>And then you can refer to this id in the route:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: xml; gutter: false; theme: Default" data-theme="Default">       &lt;route&gt;
+            &lt;from uri="direct:back"/&gt;
+            &lt;unmarshal ref="jack"/&gt;
+            &lt;to uri="mock:reverse"/&gt;
         &lt;/route&gt;
-]]></script>
-</div></div><h3 id="JacksonXML-ExcludingPOJOfieldsfrommarshalling">Excluding POJO fields from marshalling</h3><p>When marshalling a POJO to XML you might want to exclude certain fields from the XML output. With Jackson you can use&#160;<a shape="rect" class="external-link" href="http://wiki.fasterxml.com/JacksonJsonViews" rel="nofollow">JSON views</a>&#160;to accomplish this. First create one or more marker classes.</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[
+</pre>
+</div></div><h3 id="JacksonXML-ExcludingPOJOfieldsfrommarshalling">Excluding POJO fields from marshalling</h3><p>When marshalling a POJO to XML you might want to exclude certain fields from the XML output. With Jackson you can use&#160;<a shape="rect" class="external-link" href="http://wiki.fasterxml.com/JacksonJsonViews" rel="nofollow">JSON views</a>&#160;to accomplish this. First create one or more marker classes.Error rendering macro 'code': Invalid value specified for parameter 'java.lang.NullPointerException'</p><pre class="conf-macro output-inline" data-hasbody="true" data-macro-name="unmigrated-inline-wiki-markup">
 public class Views {
 
     static class Age {
@@ -118,9 +117,7 @@ public class Views {
     static class Weight {
     }
 }
-]]></script>
-</div></div>Use the marker classes with the&#160;<code>@JsonView</code>&#160;annotation to include/exclude certain fields. The annotation also works on getters.<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[
+</pre>Use the marker classes with the&#160;<code>@JsonView</code>&#160;annotation to include/exclude certain fields. The annotation also works on getters.Error rendering macro 'code': Invalid value specified for parameter 'java.lang.NullPointerException'<pre class="conf-macro output-inline" data-hasbody="true" data-macro-name="unmigrated-inline-wiki-markup">
 @JsonView(Views.Age.class)
 private int age = 30;
 
@@ -128,103 +125,100 @@ private int height = 190;
 
 @JsonView(Views.Weight.class)
 private int weight = 70;
-]]></script>
-</div></div>Finally use the Camel&#160;<code>JacksonXMLDataFormat</code>&#160;to marshall the above POJO to XML.<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-from(&quot;direct:inPojoAgeView&quot;).marshal().jacksonxml(TestPojoView.class, Views.Age.class);
-]]></script>
-</div></div>Note that the weight field is missing in the resulting XML:<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[&lt;pojo age=&quot;30&quot; weight=&quot;70&quot;/&gt;]]></script>
-</div></div><h3 id="JacksonXML-Include/ExcludefieldsusingthejsonViewattributewithJacksonXMLDataFormat">Include/Exclude fields using the&#160;<code>jsonView</code>&#160;attribute with&#160;<code>JacksonXML</code>DataFormat</h3><p>As an example of using this attribute you can instead of:</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[JacksonXMLDataFormat ageViewFormat = new JacksonXMLDataFormat(TestPojoView.class, Views.Age.class);
-from(&quot;direct:inPojoAgeView&quot;).
+</pre>Finally use the Camel&#160;<code>JacksonXMLDataFormat</code>&#160;to marshall the above POJO to XML.Error rendering macro 'code': Invalid value specified for parameter 'java.lang.NullPointerException'<pre class="conf-macro output-inline" data-hasbody="true" data-macro-name="unmigrated-inline-wiki-markup">
+from("direct:inPojoAgeView").marshal().jacksonxml(TestPojoView.class, Views.Age.class);
+</pre>Note that the weight field is missing in the resulting XML:<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">&lt;pojo age="30" weight="70"/&gt;</pre>
+</div></div><h3 id="JacksonXML-Include/ExcludefieldsusingthejsonViewattributewithJacksonXMLDataFormat">Include/Exclude fields using the&#160;<code>jsonView</code>&#160;attribute with&#160;<code>JacksonXML</code>DataFormat</h3><p>As an example of using this attribute you can instead of:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">JacksonXMLDataFormat ageViewFormat = new JacksonXMLDataFormat(TestPojoView.class, Views.Age.class);
+from("direct:inPojoAgeView").
   marshal(ageViewFormat);
-]]></script>
-</div></div><p>Directly specify your&#160;<a shape="rect" class="external-link" href="http://wiki.fasterxml.com/JacksonJsonViews" rel="nofollow">JSON view</a>&#160;inside the Java DSL as:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[from(&quot;direct:inPojoAgeView&quot;).
+</pre>
+</div></div><p>Directly specify your&#160;<a shape="rect" class="external-link" href="http://wiki.fasterxml.com/JacksonJsonViews" rel="nofollow">JSON view</a>&#160;inside the Java DSL as:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">from("direct:inPojoAgeView").
   marshal().jacksonxml(TestPojoView.class, Views.Age.class);
-]]></script>
-</div></div><p>And the same 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[&lt;from uri=&quot;direct:inPojoAgeView&quot;/&gt;
+</pre>
+</div></div><p>And the same in XML DSL:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: xml; gutter: false; theme: Default" data-theme="Default">&lt;from uri="direct:inPojoAgeView"/&gt;
   &lt;marshal&gt;
-    &lt;jacksonxml unmarshalTypeName=&quot;org.apache.camel.component.jacksonxml.TestPojoView&quot; jsonView=&quot;org.apache.camel.component.jacksonxml.Views$Age&quot;/&gt;
+    &lt;jacksonxml unmarshalTypeName="org.apache.camel.component.jacksonxml.TestPojoView" jsonView="org.apache.camel.component.jacksonxml.Views$Age"/&gt;
   &lt;/marshal&gt;
-]]></script>
-</div></div><h3 id="JacksonXML-Settingserializationincludeoption">Setting serialization include option</h3><p>If you want to marshal a pojo to XML, and the pojo has some fields with null values. And you want to skip these null values, then you need to set either an annotation on the pojo,&#160;</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[@JsonInclude(Include.NON_NULL)
+</pre>
+</div></div><h3 id="JacksonXML-Settingserializationincludeoption">Setting serialization include option</h3><p>If you want to marshal a pojo to XML, and the pojo has some fields with null values. And you want to skip these null values, then you need to set either an annotation on the pojo,&#160;</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">@JsonInclude(Include.NON_NULL)
 public class MyPojo {
    ...
-}]]></script>
-</div></div><p>But this requires you to include that annotation in your pojo source code. You can also configure the Camel JacksonXMLDataFormat to set the include option, as shown below:</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[JacksonXMLDataFormat format = new JacksonXMLDataFormat();
-format.setInclude(&quot;NON_NULL&quot;);]]></script>
-</div></div><p>Or from XML DSL you configure this as</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[    &lt;dataFormats&gt;
-      &lt;jacksonxml id=&quot;jacksonxml&quot; include=&quot;NOT_NULL&quot;/&gt;
-    &lt;/dataFormats&gt;]]></script>
-</div></div><h3 id="JacksonXML-UnmarshallingfromXMLtoPOJOwithdynamicclassname">Unmarshalling from XML to POJO with dynamic class name</h3><p>If you use jackson to unmarshal XML to POJO, then you can now specify a header in the message that indicate which class name to unmarshal to.<br clear="none"><span>The header has key&#160;</span><code>CamelJacksonUnmarshalType</code><span>&#160;if that header is present in the message, then Jackson will use that as FQN for the POJO class to unmarshal the XML payload as.</span></p><p><span>&#160;</span><span>For JMS end users there is the JMSType header from the JMS spec that indicates that also. To enable support for JMSType you would need to turn that on, on the jackson data format as shown:</span></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[JacksonDataFormat format = new JacksonDataFormat();
-format.setAllowJmsType(true);]]></script>
-</div></div><p>Or from XML DSL you configure this as</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[    &lt;dataFormats&gt;
-      &lt;jacksonxml id=&quot;jacksonxml&quot; allowJmsType=&quot;true&quot;/&gt;
-    &lt;/dataFormats&gt;]]></script>
-</div></div><h3 id="JacksonXML-UnmarshallingfromXMLtoList&lt;Map&gt;orList&lt;pojo&gt;">Unmarshalling from XML&#160;to List&lt;Map&gt; or List&lt;pojo&gt;</h3><p>If you are using Jackson to unmarshal XML to a list of map/pojo, you can now specify this by setting&#160;<code>useList="true"</code>&#160;or use the&#160;<code>org.apache.camel.component.jacksonxml.ListJacksonXMLDataFormat</code>. For example with Java you can do as shown below:</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[JacksonXMLDataFormat format = new ListJacksonXMLDataFormat();
+}</pre>
+</div></div><p>But this requires you to include that annotation in your pojo source code. You can also configure the Camel JacksonXMLDataFormat to set the include option, as shown below:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">JacksonXMLDataFormat format = new JacksonXMLDataFormat();
+format.setInclude("NON_NULL");</pre>
+</div></div><p>Or from XML DSL you configure this as</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">    &lt;dataFormats&gt;
+      &lt;jacksonxml id="jacksonxml" include="NOT_NULL"/&gt;
+    &lt;/dataFormats&gt;</pre>
+</div></div><h3 id="JacksonXML-UnmarshallingfromXMLtoPOJOwithdynamicclassname">Unmarshalling from XML to POJO with dynamic class name</h3><p>If you use jackson to unmarshal XML to POJO, then you can now specify a header in the message that indicate which class name to unmarshal to.<br clear="none"><span>The header has key&#160;</span><code>CamelJacksonUnmarshalType</code><span>&#160;if that header is present in the message, then Jackson will use that as FQN for the POJO class to unmarshal the XML payload as.</span></p><p><span>&#160;</span><span>For JMS end users there is the JMSType header from the JMS spec that indicates that also. To enable support for JMSType you would need to turn that on, on the jackson data format as shown:</span></p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">JacksonDataFormat format = new JacksonDataFormat();
+format.setAllowJmsType(true);</pre>
+</div></div><p>Or from XML DSL you configure this as</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">    &lt;dataFormats&gt;
+      &lt;jacksonxml id="jacksonxml" allowJmsType="true"/&gt;
+    &lt;/dataFormats&gt;</pre>
+</div></div><h3 id="JacksonXML-UnmarshallingfromXMLtoList&lt;Map&gt;orList&lt;pojo&gt;">Unmarshalling from XML&#160;to List&lt;Map&gt; or List&lt;pojo&gt;</h3><p>If you are using Jackson to unmarshal XML to a list of map/pojo, you can now specify this by setting&#160;<code>useList="true"</code>&#160;or use the&#160;<code>org.apache.camel.component.jacksonxml.ListJacksonXMLDataFormat</code>. For example with Java you can do as shown below:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">JacksonXMLDataFormat format = new ListJacksonXMLDataFormat();
 // or
 JacksonXMLDataFormat format = new JacksonXMLDataFormat();
 format.useList();
 // and you can specify the pojo class type also
-format.setUnmarshalType(MyPojo.class);]]></script>
-</div></div><p>And if you use XML DSL then you configure to use list using&#160;<code>useList</code>&#160;attribute as shown below:</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[    &lt;dataFormats&gt;
-      &lt;jacksonxml id=&quot;jack&quot; useList=&quot;true&quot;/&gt;
-    &lt;/dataFormats&gt;]]></script>
-</div></div><p>And you can specify the pojo type also</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[    &lt;dataFormats&gt;
-      &lt;jacksonxml id=&quot;jack&quot; useList=&quot;true&quot; unmarshalTypeName=&quot;com.foo.MyPojo&quot;/&gt;
-    &lt;/dataFormats&gt;]]></script>
-</div></div><h3 id="JacksonXML-UsingcustomJacksonmodules">Using custom Jackson modules</h3><p>You can use custom Jackson modules by specifying the class names of those using the moduleClassNames option as shown below.</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[    &lt;dataFormats&gt;
-      &lt;jacksonxml id=&quot;jack&quot; useList=&quot;true&quot; unmarshalTypeName=&quot;com.foo.MyPojo&quot; moduleClassNames=&quot;com.foo.MyModule,com.foo.MyOtherModule&quot;/&gt;
-    &lt;/dataFormats&gt;]]></script>
-</div></div><p>When using&#160;moduleClassNames then the custom jackson modules are not configured, by created using default constructor and used as-is. If a custom module needs any custom configuration, then an instance of the module can be created and configured, and then use modulesRefs to refer to the module as shown below:</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[    &lt;bean id=&quot;myJacksonModule&quot; class=&quot;com.foo.MyModule&quot;&gt;
+format.setUnmarshalType(MyPojo.class);</pre>
+</div></div><p>And if you use XML DSL then you configure to use list using&#160;<code>useList</code>&#160;attribute as shown below:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">    &lt;dataFormats&gt;
+      &lt;jacksonxml id="jack" useList="true"/&gt;
+    &lt;/dataFormats&gt;</pre>
+</div></div><p>And you can specify the pojo type also</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">    &lt;dataFormats&gt;
+      &lt;jacksonxml id="jack" useList="true" unmarshalTypeName="com.foo.MyPojo"/&gt;
+    &lt;/dataFormats&gt;</pre>
+</div></div><h3 id="JacksonXML-UsingcustomJacksonmodules">Using custom Jackson modules</h3><p>You can use custom Jackson modules by specifying the class names of those using the moduleClassNames option as shown below.</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">    &lt;dataFormats&gt;
+      &lt;jacksonxml id="jack" useList="true" unmarshalTypeName="com.foo.MyPojo" moduleClassNames="com.foo.MyModule,com.foo.MyOtherModule"/&gt;
+    &lt;/dataFormats&gt;</pre>
+</div></div><p>When using&#160;moduleClassNames then the custom jackson modules are not configured, by created using default constructor and used as-is. If a custom module needs any custom configuration, then an instance of the module can be created and configured, and then use modulesRefs to refer to the module as shown below:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">    &lt;bean id="myJacksonModule" class="com.foo.MyModule"&gt;
       ... // configure the module as you want
     &lt;/bean&gt;
- 
+&#160;
     &lt;dataFormats&gt;
-      &lt;jacksonxml id=&quot;jacksonxml&quot; useList=&quot;true&quot; unmarshalTypeName=&quot;com.foo.MyPojo&quot; moduleRefs=&quot;myJacksonModule&quot;/&gt;
-    &lt;/dataFormats&gt;]]></script>
-</div></div><p>&#160;Multiple modules can be specified separated by comma, such as moduleRefs="myJacksonModule,myOtherModule"</p><h3 id="JacksonXML-EnablingordisablefeaturesusingJackson">Enabling or disable features using Jackson</h3><p>Jackson has a number of features you can enable or disable, which its ObjectMapper uses. For example to disable failing on unknown properties when marshalling, you can configure this using the disableFeatures:</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[ &lt;dataFormats&gt;
-      &lt;jacksonxml id=&quot;jacksonxml&quot; unmarshalTypeName=&quot;com.foo.MyPojo&quot; disableFeatures=&quot;FAIL_ON_UNKNOWN_PROPERTIES&quot;/&gt;
- &lt;/dataFormats&gt;]]></script>
-</div></div><p>You can disable multiple features by separating the values using comma. The values for the features must be the name of the enums from Jackson from the following enum classes</p><ul><li>com.fasterxml.jackson.databind.SerializationFeature</li><li>com.fasterxml.jackson.databind.DeserializationFeature</li><li>com.fasterxml.jackson.databind.MapperFeature</li></ul><p>To enable a feature use the enableFeatures options instead.</p><p>From Java code you can use the type safe methods from camel-jackson module:</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[JacksonDataFormat df = new JacksonDataFormat(MyPojo.class);
+      &lt;jacksonxml id="jacksonxml" useList="true" unmarshalTypeName="com.foo.MyPojo" moduleRefs="myJacksonModule"/&gt;
+    &lt;/dataFormats&gt;</pre>
+</div></div><p>&#160;Multiple modules can be specified separated by comma, such as moduleRefs="myJacksonModule,myOtherModule"</p><h3 id="JacksonXML-EnablingordisablefeaturesusingJackson">Enabling or disable features using Jackson</h3><p>Jackson has a number of features you can enable or disable, which its ObjectMapper uses. For example to disable failing on unknown properties when marshalling, you can configure this using the disableFeatures:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default"> &lt;dataFormats&gt;
+      &lt;jacksonxml id="jacksonxml" unmarshalTypeName="com.foo.MyPojo" disableFeatures="FAIL_ON_UNKNOWN_PROPERTIES"/&gt;
+ &lt;/dataFormats&gt;</pre>
+</div></div><p>You can disable multiple features by separating the values using comma. The values for the features must be the name of the enums from Jackson from the following enum classes</p><ul><li>com.fasterxml.jackson.databind.SerializationFeature</li><li>com.fasterxml.jackson.databind.DeserializationFeature</li><li>com.fasterxml.jackson.databind.MapperFeature</li></ul><p>To enable a feature use the enableFeatures options instead.</p><p>From Java code you can use the type safe methods from camel-jackson module:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">JacksonDataFormat df = new JacksonDataFormat(MyPojo.class);
 df.disableFeature(DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES);
-df.disableFeature(DeserializationFeature.FAIL_ON_NULL_FOR_PRIMITIVES);]]></script>
-</div></div><h3 id="JacksonXML-ConvertingMapstoPOJOusingJackson">Converting Maps to POJO using Jackson</h3><p>Jackson&#160;<code>ObjectMapper</code>&#160;can be used to convert maps to POJO objects. Jackson component comes with the data converter that can be used to convert&#160;<code>java.util.Map</code>&#160;instance to non-String, non-primitive and non-Number objects.</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[Map&lt;String, Object&gt; invoiceData = new HashMap&lt;String, Object&gt;();
-invoiceData.put(&quot;netValue&quot;, 500);
-producerTemplate.sendBody(&quot;direct:mapToInvoice&quot;, invoiceData);
+df.disableFeature(DeserializationFeature.FAIL_ON_NULL_FOR_PRIMITIVES);</pre>
+</div></div><h3 id="JacksonXML-ConvertingMapstoPOJOusingJackson">Converting Maps to POJO using Jackson</h3><p>Jackson&#160;<code>ObjectMapper</code>&#160;can be used to convert maps to POJO objects. Jackson component comes with the data converter that can be used to convert&#160;<code>java.util.Map</code>&#160;instance to non-String, non-primitive and non-Number objects.</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">Map&lt;String, Object&gt; invoiceData = new HashMap&lt;String, Object&gt;();
+invoiceData.put("netValue", 500);
+producerTemplate.sendBody("direct:mapToInvoice", invoiceData);
 ...
 // Later in the processor
-Invoice invoice = exchange.getIn().getBody(Invoice.class);]]></script>
-</div></div><p>If there is a single&#160;<code>ObjectMapper</code>&#160;instance available in the Camel registry, it will used by the converter to perform the conversion. Otherwise the default mapper will be used. &#160;</p><h3 id="JacksonXML-FormattedXMLmarshalling(pretty-printing)">Formatted XML marshalling (pretty-printing)</h3><p>Using the&#160;<code>prettyPrint</code>&#160;option&#160;one can output a well formatted XML&#160;while marshalling:</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[ &lt;dataFormats&gt;
-      &lt;jacksonxml id=&quot;jack&quot; prettyPrint=&quot;true&quot;/&gt;
- &lt;/dataFormats&gt;]]></script>
-</div></div><p><span>And in Java DSL:</span></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[from(&quot;direct:inPretty&quot;).marshal().jacksonxml(true);]]></script>
-</div></div><p><span>Please note that there are 5 different overloaded&#160;<code>jacksonxml()</code>&#160;DSL methods which support the&#160;<code>prettyPrint</code>&#160;option in combination with other settings for&#160;<code>unmarshalType</code>,&#160;<code>jsonView</code>&#160;etc.&#160;</span></p><h3 id="JacksonXML-Dependencies">Dependencies</h3><p>To use Jackson XML in your camel routes you need to add the dependency on <strong>camel-jacksonxml</strong> which implements this data format.</p><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: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[&lt;dependency&gt;
+Invoice invoice = exchange.getIn().getBody(Invoice.class);</pre>
+</div></div><p>If there is a single&#160;<code>ObjectMapper</code>&#160;instance available in the Camel registry, it will used by the converter to perform the conversion. Otherwise the default mapper will be used. &#160;</p><h3 id="JacksonXML-FormattedXMLmarshalling(pretty-printing)">Formatted XML marshalling (pretty-printing)</h3><p>Using the&#160;<code>prettyPrint</code>&#160;option&#160;one can output a well formatted XML&#160;while marshalling:</p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default"> &lt;dataFormats&gt;
+      &lt;jacksonxml id="jack" prettyPrint="true"/&gt;
+ &lt;/dataFormats&gt;</pre>
+</div></div><p><span>And in Java DSL:</span></p><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">from("direct:inPretty").marshal().jacksonxml(true);</pre>
+</div></div><p><span>Please note that there are 5 different overloaded&#160;<code>jacksonxml()</code>&#160;DSL methods which support the&#160;<code>prettyPrint</code>&#160;option in combination with other settings for&#160;<code>unmarshalType</code>,&#160;<code>jsonView</code>&#160;etc.&#160;</span></p><h3 id="JacksonXML-Dependencies">Dependencies</h3><p>To use Jackson XML in your camel routes you need to add the dependency on <strong>camel-jacksonxml</strong> which implements this data format.</p><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 conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">&lt;dependency&gt;
   &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
   &lt;artifactId&gt;camel-jacksonxml&lt;/artifactId&gt;
   &lt;version&gt;x.x.x&lt;/version&gt;
   &lt;!-- use the same version as your Camel core version --&gt;
 &lt;/dependency&gt;
-]]></script>
+</pre>
 </div></div></div>
         </td>
         <td valign="top">

Modified: websites/production/camel/content/java-dsl.html
==============================================================================
--- websites/production/camel/content/java-dsl.html (original)
+++ websites/production/camel/content/java-dsl.html Mon May 21 05:25:23 2018
@@ -96,8 +96,8 @@
 <p>This is best illustrate by an example. In the code below we create a new class called <code>MyRouteBuilder</code> that extends the <code>org.apache.camel.builder.RouteBuilder</code> from Camel.<br clear="none">
 In the <code>configure</code> method the Java DSL is at our disposal.</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[
+<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
 import org.apache.camel.builder.RouteBuilder;
 
 /**
@@ -106,118 +106,106 @@ import org.apache.camel.builder.RouteBui
 public class MyRouteBuilder extends RouteBuilder {
 
     /**
-     * Let&#39;s configure the Camel routing rules using Java code...
+     * Let's configure the Camel routing rules using Java code...
      */
     public void configure() {
 
         // here is a sample which processes the input files
-        // (leaving them in place - see the &#39;noop&#39; flag)
+        // (leaving them in place - see the 'noop' flag)
         // then performs content based routing on the message using XPath
-        from(&quot;file:src/data?noop=true&quot;)
+        from("file:src/data?noop=true")
             .choice()
-                .when(xpath(&quot;/person/city = &#39;London&#39;&quot;))
-                    .to(&quot;file:target/messages/uk&quot;)
+                .when(xpath("/person/city = 'London'"))
+                    .to("file:target/messages/uk")
                 .otherwise()
-                    .to(&quot;file:target/messages/others&quot;);
+                    .to("file:target/messages/others");
     }
 
 }
-]]></script>
+</pre>
 </div></div>
 
 <p>In the <code>configure</code> method we can define Camel <a shape="rect" href="routes.html">Routes</a>. In the example above we have a single route, which pickup <a shape="rect" class="unresolved" href="#">File</a>s, (eg the from).</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-        from(&quot;file:src/data?noop=true&quot;)
-]]></script>
+<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
+        from("file:src/data?noop=true")
+</pre>
 </div></div>
 
 <p>Then we use the <a shape="rect" href="content-based-router.html">Content Based Router</a> (eg the choice) to route the message depending if the person is from London or not.</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[
+<div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">
             .choice()
-                .when(xpath(&quot;/person/city = &#39;London&#39;&quot;))
-                    .to(&quot;file:target/messages/uk&quot;)
+                .when(xpath("/person/city = 'London'"))
+                    .to("file:target/messages/uk")
                 .otherwise()
-                    .to(&quot;file:target/messages/others&quot;);
-]]></script>
+                    .to("file:target/messages/others");
+</pre>
 </div></div>
 
-<h2 id="JavaDSL-Routes">Routes</h2><p>Camel supports the definition of routing rules using a Java <a shape="rect" href="dsl.html">DSL</a> (domain specific language) which avoids the need for cumbersome XML using a <a shape="rect" href="routebuilder.html">RouteBuilder</a>.</p><p>For example a simple route can be created as follows.</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[
+<div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h2 id="JavaDSL-Routes">Routes</h2><p>Camel supports the definition of routing rules using a Java <a shape="rect" href="dsl.html">DSL</a> (domain specific language) which avoids the need for cumbersome XML using a <a shape="rect" href="routebuilder.html">RouteBuilder</a>.</p><p>For example a simple route can be created as follows.</p>Error rendering macro 'code': Invalid value specified for parameter 'java.lang.NullPointerException'<pre class="conf-macro output-inline" data-hasbody="true" data-macro-name="unmigrated-inline-wiki-markup">
 RouteBuilder builder = new RouteBuilder() {
     public void configure() {
-        errorHandler(deadLetterChannel(&quot;mock:error&quot;));
+        errorHandler(deadLetterChannel("mock:error"));
 
-        from(&quot;direct:a&quot;).to(&quot;direct:b&quot;);
+        from("direct:a").to("direct:b");
     }
 };
-]]></script>
-</div></div><p>As you can see from the above Camel uses <a shape="rect" href="uris.html">URIs</a> to wire endpoints together.</p><h3 id="JavaDSL-URIStringformatting">URI String formatting</h3><p><strong>Available as of Camel 2.0</strong></p><p>If you have endpoint URIs that accept options and you want to be able to substitute the value, e.g. build the URI by concat the strings together, then you can use the <code>java.lang.String.format</code> method. But in Camel 2.0 we have added two convenient methods in the Java DSL so you can do <code>fromF</code> and <code>toF</code> that uses String formatting to build the URI.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-from(&quot;direct:start&quot;).toF(&quot;file://%s?fileName=%s&quot;, path, name);
+</pre><p>As you can see from the above Camel uses <a shape="rect" href="uris.html">URIs</a> to wire endpoints together.</p><h3 id="JavaDSL-URIStringformatting">URI String formatting</h3><p><strong>Available as of Camel 2.0</strong></p><p>If you have endpoint URIs that accept options and you want to be able to substitute the value, e.g. build the URI by concat the strings together, then you can use the <code>java.lang.String.format</code> method. But in Camel 2.0 we have added two convenient methods in the Java DSL so you can do <code>fromF</code> and <code>toF</code> that uses String formatting to build the URI.</p>Error rendering macro 'code': Invalid value specified for parameter 'java.lang.NullPointerException'<pre class="conf-macro output-inline" data-hasbody="true" data-macro-name="unmigrated-inline-wiki-markup">
+from("direct:start").toF("file://%s?fileName=%s", path, name);
 
-fromF(&quot;file://%s?include=%s&quot;, path, pattern).toF(&quot;mock:%s&quot;, result);
-]]></script>
-</div></div><h3 id="JavaDSL-Filters">Filters</h3><p>You can combine simple routes with filters which can be arbitrary <a shape="rect" href="predicate.html">Predicate</a> implementations.</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[
+fromF("file://%s?include=%s", path, pattern).toF("mock:%s", result);
+</pre><h3 id="JavaDSL-Filters">Filters</h3><p>You can combine simple routes with filters which can be arbitrary <a shape="rect" href="predicate.html">Predicate</a> implementations.</p>Error rendering macro 'code': Invalid value specified for parameter 'java.lang.NullPointerException'<pre class="conf-macro output-inline" data-hasbody="true" data-macro-name="unmigrated-inline-wiki-markup">
 RouteBuilder builder = new RouteBuilder() {
     public void configure() {
-        errorHandler(deadLetterChannel(&quot;mock:error&quot;));
+        errorHandler(deadLetterChannel("mock:error"));
 
-        from(&quot;direct:a&quot;)
-            .filter(header(&quot;foo&quot;).isEqualTo(&quot;bar&quot;))
-                .to(&quot;direct:b&quot;);
+        from("direct:a")
+            .filter(header("foo").isEqualTo("bar"))
+                .to("direct:b");
     }
 };
-]]></script>
-</div></div><h3 id="JavaDSL-Choices">Choices</h3><p>With a choice you provide a list of predicates and outcomes along with an optional default otherwise clause which is invoked if none of the conditions are met.</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[
+</pre><h3 id="JavaDSL-Choices">Choices</h3><p>With a choice you provide a list of predicates and outcomes along with an optional default otherwise clause which is invoked if none of the conditions are met.</p>Error rendering macro 'code': Invalid value specified for parameter 'java.lang.NullPointerException'<pre class="conf-macro output-inline" data-hasbody="true" data-macro-name="unmigrated-inline-wiki-markup">
 RouteBuilder builder = new RouteBuilder() {
     public void configure() {
-        errorHandler(deadLetterChannel(&quot;mock:error&quot;));
+        errorHandler(deadLetterChannel("mock:error"));
 
-        from(&quot;direct:a&quot;)
+        from("direct:a")
             .choice()
-                .when(header(&quot;foo&quot;).isEqualTo(&quot;bar&quot;))
-                    .to(&quot;direct:b&quot;)
-                .when(header(&quot;foo&quot;).isEqualTo(&quot;cheese&quot;))
-                    .to(&quot;direct:c&quot;)
+                .when(header("foo").isEqualTo("bar"))
+                    .to("direct:b")
+                .when(header("foo").isEqualTo("cheese"))
+                    .to("direct:c")
                 .otherwise()
-                    .to(&quot;direct:d&quot;);
+                    .to("direct:d");
     }
 };
-]]></script>
-</div></div><h4 id="JavaDSL-Usingacustomprocessor">Using a custom processor</h4><p>Here is an example of using a custom <a shape="rect" href="processor.html">Processor</a></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[
+</pre><h4 id="JavaDSL-Usingacustomprocessor">Using a custom processor</h4><p>Here is an example of using a custom <a shape="rect" href="processor.html">Processor</a></p>Error rendering macro 'code': Invalid value specified for parameter 'java.lang.NullPointerException'<pre class="conf-macro output-inline" data-hasbody="true" data-macro-name="unmigrated-inline-wiki-markup">
 myProcessor = new Processor() {
     public void process(Exchange exchange) {
-        log.debug(&quot;Called with exchange: &quot; + exchange);
+        log.debug("Called with exchange: " + exchange);
     }
 };
 
 RouteBuilder builder = new RouteBuilder() {
     public void configure() {
-        errorHandler(deadLetterChannel(&quot;mock:error&quot;));
+        errorHandler(deadLetterChannel("mock:error"));
 
-        from(&quot;direct:a&quot;)
+        from("direct:a")
             .process(myProcessor);
     }
 };
-]]></script>
-</div></div><p>You can mix and match custom processors with filters and choices.</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[
+</pre><p>You can mix and match custom processors with filters and choices.</p>Error rendering macro 'code': Invalid value specified for parameter 'java.lang.NullPointerException'<pre class="conf-macro output-inline" data-hasbody="true" data-macro-name="unmigrated-inline-wiki-markup">
 RouteBuilder builder = new RouteBuilder() {
     public void configure() {
-        errorHandler(deadLetterChannel(&quot;mock:error&quot;));
+        errorHandler(deadLetterChannel("mock:error"));
 
-        from(&quot;direct:a&quot;)
-            .filter(header(&quot;foo&quot;).isEqualTo(&quot;bar&quot;))
+        from("direct:a")
+            .filter(header("foo").isEqualTo("bar"))
                 .process(myProcessor);
     }
 };
-]]></script>
-</div></div>
+</pre></div>
 
 <h3 id="JavaDSL-SeeAlso">See Also</h3>
 <ul class="alternate"><li><a shape="rect" href="dsl.html">DSL</a></li><li><a shape="rect" href="examples.html">Examples</a></li></ul></div>

Modified: websites/production/camel/content/jing.html
==============================================================================
--- websites/production/camel/content/jing.html (original)
+++ websites/production/camel/content/jing.html Mon May 21 05:25:23 2018
@@ -89,40 +89,38 @@
 	<tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="Jing-JingComponent">Jing Component</h2><p>The Jing component uses the <a shape="rect" class="external-link" href="http://www.thaiopensource.com/relaxng/jing.html" rel="nofollow">Jing Library</a> to perform XML validation of the message body using either</p><ul><li><a shape="rect" class="external-link" href="http://relaxng.org/" rel="nofollow">RelaxNG XML Syntax</a></li><li><a shape="rect" class="external-link" href="http://relaxng.org/compact-tutorial-20030326.html" rel="nofollow">RelaxNG Compact Syntax</a></li></ul><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: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[&lt;dependency&gt;
+<div class="wiki-content maincontent"><h2 id="Jing-JingComponent">Jing Component</h2><p>The Jing component uses the <a shape="rect" class="external-link" href="http://www.thaiopensource.com/relaxng/jing.html" rel="nofollow">Jing Library</a> to perform XML validation of the message body using either</p><ul><li><a shape="rect" class="external-link" href="http://relaxng.org/" rel="nofollow">RelaxNG XML Syntax</a></li><li><a shape="rect" class="external-link" href="http://relaxng.org/compact-tutorial-20030326.html" rel="nofollow">RelaxNG Compact Syntax</a></li></ul><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 conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">&lt;dependency&gt;
     &lt;groupId&gt;org.apache.camel&lt;/groupId&gt;
     &lt;artifactId&gt;camel-jing&lt;/artifactId&gt;
     &lt;version&gt;x.x.x&lt;/version&gt;
     &lt;!-- use the same version as your Camel core version --&gt;
 &lt;/dependency&gt;
-]]></script>
-</div></div><p>Note that the <a shape="rect" href="msv.html">MSV</a> component can also support RelaxNG XML syntax.</p><h3 id="Jing-URIformatCamel2.15orolder">URI format Camel 2.15 or older</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[rng:someLocalOrRemoteResource
-rnc:someLocalOrRemoteResource]]></script>
-</div></div><p>Where <strong>rng</strong> means use the <a shape="rect" class="external-link" href="http://relaxng.org/" rel="nofollow">RelaxNG XML Syntax</a> whereas <strong>rnc</strong> means use <a shape="rect" class="external-link" href="http://relaxng.org/compact-tutorial-20030326.html" rel="nofollow">RelaxNG Compact Syntax</a>. The following examples show possible URI values</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Example</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>rng:foo/bar.rng</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>References the XML file <strong>foo/bar.rng</strong> on the classpath</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>rnc:</p><a shape="rect" class="external-link" href="http://foo.com/bar.rnc" rel="nofollow">http://foo.com/bar.rnc</a></td><td co
 lspan="1" rowspan="1" class="confluenceTd"><p>References the RelaxNG Compact Syntax file from the URL,</p><a shape="rect" class="external-link" href="http://foo.com/bar.rnc" rel="nofollow">http://foo.com/bar.rnc</a></td></tr></tbody></table></div><p>You can append query options to the URI in the following format, <code>?option=value&amp;option=value&amp;...</code></p><h3 id="Jing-URIformatCamel2.16">URI format Camel 2.16</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[jing:someLocalOrRemoteResource]]></script>
-</div></div><p>From Camel 2.16 the component use jing as name, and you can use the option compactSyntax to turn on either RNG or RNC mode.</p><h3 id="Jing-Options">Options</h3><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>compactSyntax</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Whether to validate using RelaxNG compact syntax or not.</p></td></tr></tbody></table></div><h3 id="Jing-Example">Example</h3><p>The following <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/camel/trunk/components/camel-jing/src/test/resources/org/apache/camel/component/validator/jing/rnc-context.xml">exa
 mple</a> shows how to configure a route from the 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 <a shape="rect" class="external-link" href="http://relaxng.org/compact-tutorial-20030326.html" rel="nofollow">RelaxNG Compact Syntax</a> schema (which is supplied on the classpath).</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-&lt;camelContext xmlns=&quot;http://camel.apache.org/schema/spring&quot;&gt;
+</pre>
+</div></div><p>Note that the <a shape="rect" href="msv.html">MSV</a> component can also support RelaxNG XML syntax.</p><h3 id="Jing-URIformatCamel2.15orolder">URI format Camel 2.15 or older</h3><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">rng:someLocalOrRemoteResource
+rnc:someLocalOrRemoteResource</pre>
+</div></div><p>Where <strong>rng</strong> means use the <a shape="rect" class="external-link" href="http://relaxng.org/" rel="nofollow">RelaxNG XML Syntax</a> whereas <strong>rnc</strong> means use <a shape="rect" class="external-link" href="http://relaxng.org/compact-tutorial-20030326.html" rel="nofollow">RelaxNG Compact Syntax</a>. The following examples show possible URI values</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Example</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>rng:foo/bar.rng</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>References the XML file <strong>foo/bar.rng</strong> on the classpath</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>rnc:</p><a shape="rect" class="external-link" href="http://foo.com/bar.rnc" rel="nofollow">http://foo.com/bar.rnc</a></td><td co
 lspan="1" rowspan="1" class="confluenceTd"><p>References the RelaxNG Compact Syntax file from the URL,</p><a shape="rect" class="external-link" href="http://foo.com/bar.rnc" rel="nofollow">http://foo.com/bar.rnc</a></td></tr></tbody></table></div><p>You can append query options to the URI in the following format, <code>?option=value&amp;option=value&amp;...</code></p><h3 id="Jing-URIformatCamel2.16">URI format Camel 2.16</h3><div class="code panel pdl conf-macro output-block" data-hasbody="true" data-macro-name="code" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Default" data-theme="Default">jing:someLocalOrRemoteResource</pre>
+</div></div><p>From Camel 2.16 the component use jing as name, and you can use the option compactSyntax to turn on either RNG or RNC mode.</p><h3 id="Jing-Options">Options</h3><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>compactSyntax</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Whether to validate using RelaxNG compact syntax or not.</p></td></tr></tbody></table></div><h3 id="Jing-Example">Example</h3><p>The following <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/camel/trunk/components/camel-jing/src/test/resources/org/apache/camel/component/validator/jing/rnc-context.xml">exa
 mple</a> shows how to configure a route from the 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 <a shape="rect" class="external-link" href="http://relaxng.org/compact-tutorial-20030326.html" rel="nofollow">RelaxNG Compact Syntax</a> schema (which is supplied on the classpath).</p>Error rendering macro 'code': Invalid value specified for parameter 'java.lang.NullPointerException'<pre class="conf-macro output-inline" data-hasbody="true" data-macro-name="unmigrated-inline-wiki-markup">
+&lt;camelContext xmlns="http://camel.apache.org/schema/spring"&gt;
     &lt;route&gt;
-        &lt;from uri=&quot;direct:start&quot;/&gt;
+        &lt;from uri="direct:start"/&gt;
         &lt;doTry&gt;
-            &lt;to uri=&quot;jing:org/apache/camel/component/validator/jing/schema.rnc?compactSyntax=true&quot;/&gt;
-            &lt;to uri=&quot;mock:valid&quot;/&gt;
+            &lt;to uri="jing:org/apache/camel/component/validator/jing/schema.rnc?compactSyntax=true"/&gt;
+            &lt;to uri="mock:valid"/&gt;
             &lt;doCatch&gt;
                 &lt;exception&gt;org.apache.camel.ValidationException&lt;/exception&gt;
-                &lt;to uri=&quot;mock:invalid&quot;/&gt;
+                &lt;to uri="mock:invalid"/&gt;
             &lt;/doCatch&gt;
             &lt;doFinally&gt;
-                &lt;to uri=&quot;mock:finally&quot;/&gt;
+                &lt;to uri="mock:finally"/&gt;
             &lt;/doFinally&gt;
         &lt;/doTry&gt;
     &lt;/route&gt;
 &lt;/camelContext&gt;
-]]></script>
-</div></div><p></p><h3 id="Jing-SeeAlso">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></div>
+</pre><p></p><div class="conf-macro output-block" data-hasbody="false" data-macro-name="include"><h3 id="Jing-SeeAlso">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></div></div>
         </td>
         <td valign="top">
           <div class="navigation">