Author: buildbot
Date: Wed Sep 11 14:20:06 2013
New Revision: 878038

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/book-dataformat-appendix.html
    websites/production/camel/content/book-in-one-page.html
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/elasticsearch.html
    websites/production/camel/content/jaxb.html

Modified: websites/production/camel/content/book-dataformat-appendix.html
==============================================================================
--- websites/production/camel/content/book-dataformat-appendix.html (original)
+++ websites/production/camel/content/book-dataformat-appendix.html Wed Sep 11 
14:20:06 2013
@@ -368,6 +368,25 @@ JaxbDataFromat supports to ignore the <a
 
 <p>This feature has been tested with Woodstox 3.2.9 and Sun JDK 1.6 StAX 
implementation.</p>
 
+<p><b>New for Camel 2.12.1</b><br clear="none">
+JaxbDataFormat now allows you to customize the XMLStreamWriter used to marshal 
the stream to XML. Using this configuration, you can add your own stream writer 
to completely remove, escape, or replace non-xml characters. </p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
+<script class="theme: Default; brush: java; gutter: false" 
type="syntaxhighlighter"><![CDATA[
+   JaxbDataFormat customWriterFormat = new 
JaxbDataFormat("org.apache.camel.foo.bar");
+  customWriterFormat.setXmlStreamWriterWrapper(new TestXmlStreamWriter());
+]]></script>
+</div></div>
+
+<p>The following example shows using the Spring DSL and also enabling Camel's 
NonXML filtering:</p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
+<script class="theme: Default; brush: xml; gutter: false" 
type="syntaxhighlighter"><![CDATA[
+&lt;bean id="testXmlStreamWriterWrapper" 
class="org.apache.camel.jaxb.TestXmlStreamWriter"/&gt;
+&lt;jaxb filterNonXmlChars="true"  contextPath="org.apache.camel.foo.bar" 
xmlStreamWriterWrapper="#testXmlStreamWriterWrapper" /&gt;
+]]></script>
+</div></div>
+
 <h3><a shape="rect" 
name="BookDataFormatAppendix-WorkingwiththeObjectFactory"></a>Working with the 
ObjectFactory</h3>
 
 <p>If you use XJC to create the java class from the schema, you will get an 
ObjectFactory for you JAXB context. Since the ObjectFactory uses <a 
shape="rect" class="external-link" 
href="http://java.sun.com/javase/6/docs/api/javax/xml/bind/JAXBElement.html"; 
rel="nofollow">JAXBElement</a> to hold the reference of the schema and element 
instance value, jaxbDataformat will ignore the JAXBElement by default and you 
will get the element instance value instead of the JAXBElement object form the 
unmarshaled message body. <br clear="none">

Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Wed Sep 11 14:20:06 
2013
@@ -11461,6 +11461,25 @@ JaxbDataFromat supports to ignore the <a
 
 <p>This feature has been tested with Woodstox 3.2.9 and Sun JDK 1.6 StAX 
implementation.</p>
 
+<p><b>New for Camel 2.12.1</b><br clear="none">
+JaxbDataFormat now allows you to customize the XMLStreamWriter used to marshal 
the stream to XML. Using this configuration, you can add your own stream writer 
to completely remove, escape, or replace non-xml characters. </p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
+<script class="theme: Default; brush: java; gutter: false" 
type="syntaxhighlighter"><![CDATA[
+   JaxbDataFormat customWriterFormat = new 
JaxbDataFormat("org.apache.camel.foo.bar");
+  customWriterFormat.setXmlStreamWriterWrapper(new TestXmlStreamWriter());
+]]></script>
+</div></div>
+
+<p>The following example shows using the Spring DSL and also enabling Camel's 
NonXML filtering:</p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
+<script class="theme: Default; brush: xml; gutter: false" 
type="syntaxhighlighter"><![CDATA[
+&lt;bean id="testXmlStreamWriterWrapper" 
class="org.apache.camel.jaxb.TestXmlStreamWriter"/&gt;
+&lt;jaxb filterNonXmlChars="true"  contextPath="org.apache.camel.foo.bar" 
xmlStreamWriterWrapper="#testXmlStreamWriterWrapper" /&gt;
+]]></script>
+</div></div>
+
 <h3><a shape="rect" 
name="BookInOnePage-WorkingwiththeObjectFactory"></a>Working with the 
ObjectFactory</h3>
 
 <p>If you use XJC to create the java class from the schema, you will get an 
ObjectFactory for you JAXB context. Since the ObjectFactory uses <a 
shape="rect" class="external-link" 
href="http://java.sun.com/javase/6/docs/api/javax/xml/bind/JAXBElement.html"; 
rel="nofollow">JAXBElement</a> to hold the reference of the schema and element 
instance value, jaxbDataformat will ignore the JAXBElement by default and you 
will get the element instance value instead of the JAXBElement object form the 
unmarshaled message body. <br clear="none">

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

Modified: websites/production/camel/content/elasticsearch.html
==============================================================================
--- websites/production/camel/content/elasticsearch.html (original)
+++ websites/production/camel/content/elasticsearch.html Wed Sep 11 14:20:06 
2013
@@ -106,7 +106,7 @@
 
 <div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
 <script class="theme: Default; brush: java; gutter: false" 
type="syntaxhighlighter"><![CDATA[
-elasticsearch://[clusterName]?[options]
+elasticsearch://clusterName[?options]
 ]]></script>
 </div></div>
 

Modified: websites/production/camel/content/jaxb.html
==============================================================================
--- websites/production/camel/content/jaxb.html (original)
+++ websites/production/camel/content/jaxb.html Wed Sep 11 14:20:06 2013
@@ -205,6 +205,25 @@ JaxbDataFromat supports to ignore the <a
 
 <p>This feature has been tested with Woodstox 3.2.9 and Sun JDK 1.6 StAX 
implementation.</p>
 
+<p><b>New for Camel 2.12.1</b><br clear="none">
+JaxbDataFormat now allows you to customize the XMLStreamWriter used to marshal 
the stream to XML. Using this configuration, you can add your own stream writer 
to completely remove, escape, or replace non-xml characters. </p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
+<script class="theme: Default; brush: java; gutter: false" 
type="syntaxhighlighter"><![CDATA[
+   JaxbDataFormat customWriterFormat = new 
JaxbDataFormat("org.apache.camel.foo.bar");
+  customWriterFormat.setXmlStreamWriterWrapper(new TestXmlStreamWriter());
+]]></script>
+</div></div>
+
+<p>The following example shows using the Spring DSL and also enabling Camel's 
NonXML filtering:</p>
+
+<div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
+<script class="theme: Default; brush: xml; gutter: false" 
type="syntaxhighlighter"><![CDATA[
+&lt;bean id="testXmlStreamWriterWrapper" 
class="org.apache.camel.jaxb.TestXmlStreamWriter"/&gt;
+&lt;jaxb filterNonXmlChars="true"  contextPath="org.apache.camel.foo.bar" 
xmlStreamWriterWrapper="#testXmlStreamWriterWrapper" /&gt;
+]]></script>
+</div></div>
+
 <h3><a shape="rect" name="JAXB-WorkingwiththeObjectFactory"></a>Working with 
the ObjectFactory</h3>
 
 <p>If you use XJC to create the java class from the schema, you will get an 
ObjectFactory for you JAXB context. Since the ObjectFactory uses <a 
shape="rect" class="external-link" 
href="http://java.sun.com/javase/6/docs/api/javax/xml/bind/JAXBElement.html"; 
rel="nofollow">JAXBElement</a> to hold the reference of the schema and element 
instance value, jaxbDataformat will ignore the JAXBElement by default and you 
will get the element instance value instead of the JAXBElement object form the 
unmarshaled message body. <br clear="none">


Reply via email to