Author: buildbot
Date: Mon Apr 16 11:57:26 2018
New Revision: 1028496
Log:
Production update by buildbot for cxf
Modified:
websites/production/cxf/content/cache/docs.pageCache
websites/production/cxf/content/docs/sdo.html
websites/production/cxf/content/docs/xmlbeans.html
Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/cxf/content/docs/sdo.html
==============================================================================
--- websites/production/cxf/content/docs/sdo.html (original)
+++ websites/production/cxf/content/docs/sdo.html Mon Apr 16 11:57:26 2018
@@ -32,8 +32,8 @@
<link type="text/css" rel="stylesheet"
href="/resources/highlighter/styles/shThemeCXF.css">
<script src='/resources/highlighter/scripts/shCore.js'></script>
-<script src='/resources/highlighter/scripts/shBrushBash.js'></script>
<script src='/resources/highlighter/scripts/shBrushJava.js'></script>
+<script src='/resources/highlighter/scripts/shBrushBash.js'></script>
<script>
SyntaxHighlighter.defaults['toolbar'] = false;
SyntaxHighlighter.all();
@@ -117,14 +117,8 @@ Apache CXF -- SDO
<td height="100%">
<!-- Content -->
<div class="wiki-content">
-<div id="ConfluenceContent"><p>Apache CXF 2.3 added support for the <a
shape="rect" class="external-link"
href="http://tuscany.apache.org/sdo-java.html";>Tuscany</a> implementation of <a
shape="rect" class="external-link"
href="http://en.wikipedia.org/wiki/Service_Data_Objects"; rel="nofollow">Service
Data Objects</a> as alternative data binding.</p>
-
-<h3 id="SDO-Setup">Setup</h3>
-<p>By default, CXF does not ship with the Tuscany SDO jars. You will need to
acquire them elsewhere and add them to the classpath for the SDO databinding to
work. The list of required jars are:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default"
style="font-size:12px;">
-backport-util-concurrent-3.0.jar
+<div id="ConfluenceContent"><p>Apache CXF 2.3 added support for the <a
shape="rect" class="external-link"
href="http://tuscany.apache.org/sdo-java.html";>Tuscany</a> implementation of <a
shape="rect" class="external-link"
href="http://en.wikipedia.org/wiki/Service_Data_Objects"; rel="nofollow">Service
Data Objects</a> as alternative data binding. Note that this data-binding has
been removed from Apache CXF 3.2.0 onwards, as the Apache Tuscany project has
been retired to the <a shape="rect" class="external-link"
href="http://attic.apache.org/";>attic</a>.</p><h3
id="SDO-Setup">Setup</h3><p>By default, CXF does not ship with the Tuscany SDO
jars. You will need to acquire them elsewhere and add them to the classpath for
the SDO databinding to work. The list of required jars are:</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="brush: java; gutter: false; theme: Default"
style="font-size:12px;">backport-util-concurrent-3.0.jar
codegen-2.2.3.jar
codegen-ecore-2.2.3.jar
common-2.2.3.jar
@@ -137,11 +131,7 @@ tuscany-sdo-lib-1.1.1.jar
tuscany-sdo-tools-1.1.1.jar
xsd-2.2.3.jar
</pre>
-</div></div>
-
-<h3 id="SDO-CodeGeneration">Code Generation</h3>
-
-<p>If all the SDO required jars are available (by default, CXF does not ship
them, see above), wsld2java tool can be run with the -db sdo flag to have the
code generator emit SDO objects instead of the default JAXB objects. The
generated SEI interface will have
@DataBinding(org.apache.cxf.sdo.SDODataBinding.class) annotation on it which is
enough to configure the runtime to know to use SDO.</p></div>
+</div></div><h3 id="SDO-CodeGeneration">Code Generation</h3><p>If all the SDO
required jars are available (by default, CXF does not ship them, see above),
wsld2java tool can be run with the -db sdo flag to have the code generator emit
SDO objects instead of the default JAXB objects. The generated SEI interface
will have @DataBinding(org.apache.cxf.sdo.SDODataBinding.class) annotation on
it which is enough to configure the runtime to know to use SDO.</p></div>
</div>
<!-- Content -->
</td>
Modified: websites/production/cxf/content/docs/xmlbeans.html
==============================================================================
--- websites/production/cxf/content/docs/xmlbeans.html (original)
+++ websites/production/cxf/content/docs/xmlbeans.html Mon Apr 16 11:57:26 2018
@@ -32,8 +32,8 @@
<link type="text/css" rel="stylesheet"
href="/resources/highlighter/styles/shThemeCXF.css">
<script src='/resources/highlighter/scripts/shCore.js'></script>
-<script src='/resources/highlighter/scripts/shBrushXml.js'></script>
<script src='/resources/highlighter/scripts/shBrushJava.js'></script>
+<script src='/resources/highlighter/scripts/shBrushXml.js'></script>
<script>
SyntaxHighlighter.defaults['toolbar'] = false;
SyntaxHighlighter.all();
@@ -117,33 +117,15 @@ Apache CXF -- XMLBeans
<td height="100%">
<!-- Content -->
<div class="wiki-content">
-<div id="ConfluenceContent"><p><a shape="rect" class="external-link"
href="http://xmlbeans.apache.org/";>Apache XMLBeans</a> is another technology
for mapping XML Schema to java objects. CXF added support for XMLBeans in
2.1. There are a two parts to the support for XMLBeans:</p>
-
-<h3 id="XMLBeans-CodeGeneration">Code Generation</h3>
-
-<p>The wsdl2java tool now allows a "-db xmlbeans" flag to be added that will
generate XMLBeans types for all the schema beans instead of the default JAXB
beans. With 2.1 and 2.2, the types are generated, but you still need to
configure the XMLBeans databinding to be used at runtime. With 2.3, the
generated code contains an @Databinding annotation marking it as XMLBeans and
the configuration is unnecessary. </p>
-
-
-<h3 id="XMLBeans-Runtime">Runtime</h3>
-
-<p>You need to configure the runtime to tell it to use XMLBeans for the
databinding instead of JAXB. </p>
-
-<h4 id="XMLBeans-Springconfig">Spring config</h4>
-<p>For the server side, your spring configuration would contain something
like:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default"
style="font-size:12px;">
-<jaxws:server serviceClass="demo.hw.server.HelloWorld"
address="/hello_world">
+<div id="ConfluenceContent"><p><a shape="rect" class="external-link"
href="http://xmlbeans.apache.org/";>Apache XMLBeans</a> is another technology
for mapping XML Schema to java objects. CXF added support for XMLBeans in 2.1.
Note that this data-binding has been removed from Apache CXF 3.2.0 onwards, as
Apache XMLBeans has been retired to the <a shape="rect" class="external-link"
href="http://attic.apache.org/";>attic</a>.</p><p> </p><p>There are a two
parts to the support for XMLBeans:</p><h3 id="XMLBeans-CodeGeneration">Code
Generation</h3><p>The wsdl2java tool now allows a "-db xmlbeans" flag to be
added that will generate XMLBeans types for all the schema beans instead of the
default JAXB beans. With 2.1 and 2.2, the types are generated, but you still
need to configure the XMLBeans databinding to be used at runtime. With 2.3, the
generated code contains an @Databinding annotation marking it as XMLBeans and
the configuration is unnecessary.</p><h3 id="XMLBeans-Runtime">Runtime
</h3><p>You need to configure the runtime to tell it to use XMLBeans for the
databinding instead of JAXB.</p><h4 id="XMLBeans-Springconfig">Spring
config</h4><p>For the server side, your spring configuration would contain
something like:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<pre class="brush: java; gutter: false; theme: Default"
style="font-size:12px;"><jaxws:server
serviceClass="demo.hw.server.HelloWorld" address="/hello_world">
<jaxws:dataBinding>
<bean class="org.apache.cxf.xmlbeans.XmlBeansDataBinding" />
</jaxws:dataBinding>
</jaxws:server>
</pre>
-</div></div>
-<p>or</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default"
style="font-size:12px;">
-<jaxws:endpoint
+</div></div><p>or</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<pre class="brush: java; gutter: false; theme: Default"
style="font-size:12px;"><jaxws:endpoint
id="helloWorld"
implementor="demo.spring.HelloWorldImpl"
address="http://localhost/HelloWorld">
@@ -152,12 +134,8 @@ Apache CXF -- XMLBeans
</jaxws:dataBinding>
</jaxws:endpoint>
</pre>
-</div></div>
-
-<p>The client side is very similar:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default"
style="font-size:12px;">
-<jaxws:client id="helloClient"
+</div></div><p>The client side is very similar:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="brush: java; gutter: false; theme: Default"
style="font-size:12px;"><jaxws:client id="helloClient"
serviceClass="demo.spring.HelloWorld"
address="http://localhost:9002/HelloWorld">
<jaxws:dataBinding>
@@ -165,16 +143,8 @@ Apache CXF -- XMLBeans
</jaxws:dataBinding>
<jaxws:client>
</pre>
-</div></div>
-
-
-<h4 id="XMLBeans-FactoryBeans">FactoryBeans</h4>
-
-<p>If using programmatic factory beans instead of spring configuration, the
databinding can be set on the ClientProxyFactoryBean (and subclasses) and the
ServerFactoryBean (and subclasses) via:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default"
style="font-size:12px;">
-factory.getServiceFactory().setDataBinding(new
org.apache.cxf.xmlbeans.XmlBeansDataBinding());
+</div></div><h4 id="XMLBeans-FactoryBeans">FactoryBeans</h4><p>If using
programmatic factory beans instead of spring configuration, the databinding can
be set on the ClientProxyFactoryBean (and subclasses) and the ServerFactoryBean
(and subclasses) via:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<pre class="brush: java; gutter: false; theme: Default"
style="font-size:12px;">factory.getServiceFactory().setDataBinding(new
org.apache.cxf.xmlbeans.XmlBeansDataBinding());
</pre>
</div></div></div>
</div>
