svn commit: r916183 - in /websites/production/camel/content: cache/main.pageCache splitter.html

[buildbot]

Author: buildbot
Date: Mon Jul 14 14:31:06 2014
New Revision: 916183

Log:
Production update by buildbot for camel

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

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

Modified: websites/production/camel/content/splitter.html
==============================================================================
--- websites/production/camel/content/splitter.html (original)
+++ websites/production/camel/content/splitter.html Mon Jul 14 14:31:06 2014
@@ -153,7 +153,7 @@ from("activemq:my.queue").spli
                     <p class="title">Splitting big XML payloads</p>
                             <span class="aui-icon icon-hint">Icon</span>
                 <div class="message-content">
-                            <p>The XPath engine in Java and <a shape="rect" 
href="xquery.html">saxon</a> will load the entire XML content into memory. And 
thus they are not well suited for very big XML payloads.<br clear="none"> 
Instead you can use a custom <a shape="rect" 
href="expression.html">Expression</a> which will iterate the XML payload in a 
streamed fashion. From Camel 2.9 onwards you can use the Tokenizer language<br 
clear="none"> which supports this when you supply the start and end tokens.</p>
+                            <p>The XPath engine in Java and <a shape="rect" 
href="xquery.html">saxon</a> will load the entire XML content into memory. And 
thus they are not well suited for very big XML payloads.<br clear="none"> 
Instead you can use a custom <a shape="rect" 
href="expression.html">Expression</a> which will iterate the XML payload in a 
streamed fashion. From Camel 2.9 onwards you can use the Tokenizer language<br 
clear="none"> which supports this when you supply the start and end tokens. 
From Camel 2.14, you can use the XMLTokenizer language which is 
<span>specifically </span>provided for tokenizing XML documents.</p>
                     </div>
     </div>
 <p>You can split streams by enabling the streaming mode using the 
<code>streaming</code> builder method.</p><div class="code panel pdl" 
style="border-width: 1px;"><div class="codeContent panelContent pdl">
@@ -219,7 +219,7 @@ from(&quot;direct:streaming&quot;)
     .split().tokenizeXML(&quot;order&quot;, &quot;orders&quot;).streaming()
        .to(&quot;activemq:queue:order&quot;);
 ]]></script>
-</div></div><p><span style="line-height: 1.4285715;">Available as of Camel 
2.13.1, you can set the above inheritNamsepaceTagName property to "*" 
to&#160;include the preceding context in each token (i.e., generating each 
token enclosed in its ancestor elements). It is noted that each token must 
share the same ancestor elements in this case.</span></p><p><span 
style="line-height: 1.4285715;">The above tokenizer works well on simple 
structures but has some inherent limitations in handling more complex XML 
structures.</span></p><p><strong>Available as of Camel 2.14</strong></p><p>The 
second tokenizer that uses a StAX parser to overcome these limitations. This 
tokenizer recognizes XML namespaces and also complex XML structures.</p><p>To 
split using this tokenizer at {<a shape="rect" 
rel="nofollow">urn:shop}order</a>, we can write</p><div class="code panel pdl" 
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><p><span style="line-height: 1.4285715;">Available as of Camel 
2.13.1, you can set the above inheritNamsepaceTagName property to "*" 
to&#160;include the preceding context in each token (i.e., generating each 
token enclosed in its ancestor elements). It is noted that each token must 
share the same ancestor elements in this case.</span></p><p><span 
style="line-height: 1.4285715;">The above tokenizer works well on simple 
structures but has some inherent limitations in handling more complex XML 
structures.</span></p><p><strong>Available as of Camel 2.14</strong></p><p>The 
second tokenizer uses a StAX parser to overcome these limitations. This 
tokenizer recognizes XML namespaces and also handles simple and complex XML 
structures more naturally and efficiently.&#160;</p><p>To split using this 
tokenizer at {<a shape="rect" rel="nofollow">urn:shop}order</a>, we can 
write</p><div class="code panel pdl" style="border-width: 1px;"><div 
class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" 
type="syntaxhighlighter"><![CDATA[  Namespaces ns = new 
Namespaces(&quot;ns1&quot;, &quot;urn:shop&quot;);
   ...
   from(&quot;file:inbox&quot;)