svn commit: r990689 - /websites/production/camel/content/bindy.html

[buildbot]

Author: buildbot
Date: Thu Jun 16 08:25:22 2016
New Revision: 990689

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/bindy.html

Modified: websites/production/camel/content/bindy.html
==============================================================================
--- websites/production/camel/content/bindy.html (original)
+++ websites/production/camel/content/bindy.html Thu Jun 16 08:25:22 2016
@@ -820,6 +820,11 @@ bindy.setLocale(Locale.getDefault().getI
         .to("direct:handleSingleOrder")
     .end();
 ]]></script>
+</div></div><p>Take care of the fact that Bindy uses CHARSET_NAME property or 
the CHARSET_NAME header as define in the Exchange interface to do a 
characterset conversion of the inputstream received for unmarshalling. In some 
producers (e.g. file-endpoint) you can define a characterset. The characterset 
conversion can already been done by this producer. Sometimes you need to remove 
this property or header from the exchange before sending it to the unmarshal. 
If you don't remove it the conversion might be done twice which might lead to 
unwanted results.</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://inbox?charset=Cp922&quot;)
+  .removeProperty(Exchange.CHARSET_NAME)
+  .unmarshal(&quot;myBindyDataFormat&quot;)
+  .to(&quot;direct:handleOrders&quot;);]]></script>
 </div></div><h4 id="Bindy-Marshaling">Marshaling</h4><p>To generate CSV 
records from a collection of model objects, you create the following 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[from(&quot;direct:handleOrders&quot;)
    .marshal(bindy)