Author: buildbot
Date: Fri Apr 4 13:19:07 2014
New Revision: 904914
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/cxf.html
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/cxf.html
==============================================================================
--- websites/production/camel/content/cxf.html (original)
+++ websites/production/camel/content/cxf.html Fri Apr 4 13:19:07 2014
@@ -99,11 +99,11 @@
</div>
</div>
<p>The <strong>cxf:</strong> component provides integration with <a
shape="rect" href="http://cxf.apache.org";>Apache CXF</a> for connecting to
JAX-WS services hosted in CXF.</p><p><style type="text/css">/*<![CDATA[*/
-div.rbtoc1395408039545 {padding: 0px;}
-div.rbtoc1395408039545 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1395408039545 li {margin-left: 0px;padding-left: 0px;}
+div.rbtoc1396617502408 {padding: 0px;}
+div.rbtoc1396617502408 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1396617502408 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></p><div class="toc-macro rbtoc1395408039545">
+/*]]>*/</style></p><div class="toc-macro rbtoc1396617502408">
<ul class="toc-indentation"><li><a shape="rect" href="#CXF-CXFComponent">CXF
Component</a>
<ul class="toc-indentation"><li><a shape="rect" href="#CXF-URIformat">URI
format</a></li><li><a shape="rect" href="#CXF-Options">Options</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#CXF-Thedescriptionsofthedataformats">The descriptions of the
dataformats</a>
@@ -137,18 +137,7 @@ div.rbtoc1395408039545 li {margin-left:
</div></div><p>Where <strong>someAddress</strong> specifies the CXF endpoint's
address. With this URI format, most of the endpoint details are specified using
options.</p><p>For either style above, you can append options to the URI as
follows:</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[cxf:bean:cxfEndpoint?wsdlURL=wsdl/hello_world.wsdl&dataFormat=PAYLOAD
]]></script>
-</div></div><h3 id="CXF-Options">Options</h3><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p> Required </p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>wsdlURL</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> No </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> The location of the WSDL. It is obtained
from endpoint address by default. <br clear="none" class="atl-forced-newline">
<br clear="none" class="atl-forced-newline"> <em>Example</em>: <a shape="rect"
class="external-link" href="file://local/wsdl/hello.wsdl"
rel="nofollow">file://local/wsdl/hello.wsdl</a> or <code>wsdl/hello.wsdl</code>
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>serviceClass</code> </p></td><td colspan="1" rowsp
an="1" class="confluenceTd"><p> Yes </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> The name of the SEI (Service Endpoint Interface)
class. This class can have, but does not require, JSR181 annotations. <br
clear="none" class="atl-forced-newline"> This option is only required by POJO
mode. If the wsdlURL option is provided, serviceClass is not required for
PAYLOAD and MESSAGE mode. When wsdlURL option is used without serviceClass, the
serviceName and portName (endpointName for Spring configuration) options
<strong>MUST</strong> be provided. It is possible to use <code>#</code>
notation to reference a <code>serviceClass</code> object instance from the
registry. E.g. <code>serviceClass=#beanName</code>. The
<code>serviceClass</code> for a CXF producer (that is, the <code>to</code>
endpoint) should be a Java interface.<br clear="none"
class="atl-forced-newline"> <strong>Since 2.8,</strong> it is possible to omit
both wsdlURL and serviceClass options for PAYLOAD and MESSAG
E mode. When they are omitted, arbitrary XML elements can be put in
CxfPayload's body in PAYLOAD mode to facilitate CXF Dispatch Mode. <br
clear="none" class="atl-forced-newline"> <br clear="none"
class="atl-forced-newline"> Please be advised that the <strong>referenced
object cannot be a Proxy</strong> (Spring AOP Proxy is OK) as it relies on
<code>Object.getClass().getName()</code> method for non Spring AOP Proxy. <br
clear="none" class="atl-forced-newline"> <br clear="none"
class="atl-forced-newline"> <em>Example</em>:
<code>org.apache.camel.Hello</code> </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>serviceName</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> No </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> The service name this service is
implementing, it maps to the <code>wsdl:service@name</code>. <br clear="none"
class="atl-forced-newline"> <br clear="none" class="atl-forced-newline">
<strong>Required</strong>
for camel-cxf consumer since camel-2.2.0 or if more than one
<code>serviceName</code> is present in WSDL. <br clear="none"
class="atl-forced-newline"> <br clear="none" class="atl-forced-newline">
<em>Example</em>: {http:­//org.apache.camel}ServiceName
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>portName</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> No </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> The port name this service is implementing, it maps to
the <code>wsdl:port@name</code>. <br clear="none" class="atl-forced-newline">
<br clear="none" class="atl-forced-newline"> <strong>Required</strong> for
camel-cxf consumer since camel-2.2.0 or if more than one <code>portName</code>
is present under <code>serviceName</code>. <br clear="none"
class="atl-forced-newline"> <br clear="none" class="atl-forced-newline">
<em>Example</em>: {http:­//org.apache.camel}PortName </p></td></tr><tr><td
colspan="1" rowspan=
"1" class="confluenceTd"><p> <code>dataFormat</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> No </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> The data type messages supported by the CXF endpoint.
<br clear="none" class="atl-forced-newline"> <br clear="none"
class="atl-forced-newline"> <em>Default</em>: <code>POJO</code> <br
clear="none" class="atl-forced-newline"> <em>Example</em>: <code>POJO</code>,
<code>PAYLOAD</code>, <code>MESSAGE</code> </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>relayHeaders</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> No </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> Please see the <strong>Description
of</strong> <code><strong>relayHeaders</strong></code> <strong>option</strong>
section for this option. Should a CXF endpoint relay headers along the route.
Currently only available when <code>dataFormat=POJO</code> <br clear="none"
class="atl-forced-n
ewline"> <br clear="none" class="atl-forced-newline"> <em>Default</em>:
<code>true</code> <br clear="none" class="atl-forced-newline">
<em>Example</em>: <code>true</code>, <code>false</code> </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>wrapped</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> No </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> Which kind of operation that
CXF endpoint producer will invoke <br clear="none" class="atl-forced-newline">
<br clear="none" class="atl-forced-newline"> <em>Default</em>:
<code>false</code> <br clear="none" class="atl-forced-newline">
<em>Example</em>: <code>true</code>, <code>false</code> </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>wrappedStyle</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> No </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> <strong>New in 2.5.0</strong>
The WSDL style that describes how paramet
ers are represented in the SOAP body. If the value is false, CXF will chose
the document-literal unwrapped style, If the value is true, CXF will chose the
document-literal wrapped style <br clear="none" class="atl-forced-newline"> <br
clear="none" class="atl-forced-newline"> <em>Default</em>: <code>Null</code>
<br clear="none" class="atl-forced-newline"> <em>Example</em>:
<code>true</code>, <code>false</code> </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>setDefaultBus</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> No </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> Will set the default bus when CXF endpoint
create a bus by itself <br clear="none" class="atl-forced-newline"> <br
clear="none" class="atl-forced-newline"> <em>Default</em>: <code>false</code>
<br clear="none" class="atl-forced-newline"> <em>Example</em>:
<code>true</code>, <code>false</code> </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd
"><p> <code>bus</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> No </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> A default bus created by CXF Bus Factory. Use
<code>#</code> notation to reference a bus object from the registry. The
referenced object must be an instance of <code>org.apache.cxf.Bus</code>. <br
clear="none" class="atl-forced-newline"> <br clear="none"
class="atl-forced-newline"> <em>Example</em>: <code>bus=#busName</code>
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>cxfBinding</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> No </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> Use <code>#</code> notation to reference a CXF binding
object from the registry. The referenced object must be an instance of
<code>org.apache.camel.component.cxf.CxfBinding</code> (use an instance of
<code>org.apache.camel.component.cxf.DefaultCxfBinding</code>). <br
clear="none" class="atl-force
d-newline"> <br clear="none" class="atl-forced-newline"> <em>Example</em>:
<code>cxfBinding=#bindingName</code> <br clear="none"
class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>headerFilterStrategy</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> No </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> Use <code>#</code> notation to reference a
header filter strategy object from the registry. The referenced object must be
an instance of <code>org.apache.camel.spi.HeaderFilterStrategy</code> (use an
instance of
<code>org.apache.camel.component.cxf.CxfHeaderFilterStrategy</code>). <br
clear="none" class="atl-forced-newline"> <br clear="none"
class="atl-forced-newline"> <em>Example</em>:
<code>headerFilterStrategy=#strategyName</code> </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>
<code>loggingFeatureEnabled</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> No
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> New in 2.3.
This option enables CXF Logging Feature which writes inbound and outbound SOAP
messages to log. <br clear="none" class="atl-forced-newline"> <br clear="none"
class="atl-forced-newline"> <em>Default</em>: <code>false</code> <br
clear="none" class="atl-forced-newline"> <em>Example</em>:
<code>loggingFeatureEnabled</code><code>=true</code> </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>
<code>defaultOperationName</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> No </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> New in 2.4, this option will set the default
operationName that will be used by the CxfProducer which invokes the remote
service. <br clear="none" class="atl-forced-newline"> <br clear="none"
class="atl-forced-newline"> <em>Default</em>: <code>null</code> <br
clear="none" class="atl-forced-newline"> <em>Example</em>:
<code>defaultOperationName</code
><code>=greetMe</code> </p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p> <code>defaultOperationNamespace</code> </p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p> No </p></td><td colspan="1"
>rowspan="1" class="confluenceTd"><p> New in 2.4. This option will set the
>default operationNamespace that will be used by the CxfProducer which invokes
>the remote service. <br clear="none" class="atl-forced-newline"> <br
>clear="none" class="atl-forced-newline"> <em>Default</em>: <code>null</code>
><br clear="none" class="atl-forced-newline"> <em>Example</em>:
><code>defaultOperationNamespace</code><code>=</code><code><a shape="rect"
>class="external-link"
>href="http://apache.org/hello_world_soap_http";>http://apache.org/hello_world_soap_http</a></code>
> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
><code>synchronous</code> </p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p> No </p></td><td colspan="1" rowspan="1"
>class="confluenceTd">
<p> New in 2.5. This option will let cxf endpoint decide to use sync or async
API to do the underlying work. The default value is false which means camel-cxf
endpoint will try to use async API by default. <br clear="none"
class="atl-forced-newline"> <br clear="none" class="atl-forced-newline">
<em>Default</em>: <code>false</code> <br clear="none"
class="atl-forced-newline"> <em>Example</em>: synchronous=true
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>publishedEndpointUrl</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> No </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> New in 2.5. This option can override the endpointUrl
that published from the WSDL which can be accessed with service address url
plus ?wsdl. <br clear="none" class="atl-forced-newline"> <br clear="none"
class="atl-forced-newline"> <em>Default</em>: <code>null</code> <br
clear="none" class="atl-forced-newline"> <em>Example</em>:
publshedEndpointUrl=<a
shape="rect" class="external-link" href="http://example.com/service";
rel="nofollow">http://example.com/service</a> </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>properties.XXX</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> No </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <strong>Camel 2.8:</strong> Allows to set
custom properties to CXF in the endpoint uri. For example setting
<code>properties.mtom-enabled=true</code> to enable MTOM. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>allowStreaming</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> No </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> New in 2.8.2. This option
controls whether the CXF component, when running in PAYLOAD mode (see below),
will DOM parse the incoming messages into DOM Elements or keep the payload as a
javax.xml.transform.Source object that would allow streaming in some cases. </
p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>skipFaultLogging</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> No </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> New in 2.11. This option controls whether the
PhaseInterceptorChain skips logging the Fault that it catches.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>username</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> No </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> New in <strong>Camel 2.12.3</strong> This option is
used to set the basic authentication information of username for the CXF
client. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>password</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> No </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> New in <strong>Camel 2.12.3</strong> This option is
used to set the basic authentication
information of password for the CXF client.
</p></td></tr></tbody></table></div>
-
-
-<p>The <code>serviceName</code> and <code>portName</code> are <a shape="rect"
class="external-link" href="http://en.wikipedia.org/wiki/QName";
rel="nofollow">QNames</a>, so if you provide them be sure to prefix them with
their {namespace} as shown in the examples above.</p>
-
-<h4 id="CXF-Thedescriptionsofthedataformats">The descriptions of the
dataformats</h4>
-
-
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p> DataFormat </p></th><th
colspan="1" rowspan="1" class="confluenceTh"><p> Description
</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>POJO</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
POJOs (Plain old Java objects) are the Java parameters to the method being
invoked on the target server. Both Protocol and Logical JAX-WS handlers are
supported. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>PAYLOAD</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>PAYLOAD</code> is the message
payload (the contents of the <code>soap:body</code>) after message
configuration in the CXF endpoint is applied. Only Protocol JAX-WS handler is
supported. Logical JAX-WS handler is not supported. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>MESSAGE</code
> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
> <code>MESSAGE</code> is the raw message that is received from the transport
> layer. It is not suppose to touch or change Stream, some of the CXF
> interceptor will be removed if you are using this kind of DataFormat so you
> can't see any soap headers after the camel-cxf consumer and JAX-WS handler
> is not supported. </p></td></tr><tr><td colspan="1" rowspan="1"
> class="confluenceTd"><p> <code>CXF_MESSAGE</code> </p></td><td colspan="1"
> rowspan="1" class="confluenceTd"><p> New in <strong>Camel 2.8.2</strong>,
> <code>CXF_MESSAGE</code> allows for invoking the full capabilities of CXF
> interceptors by converting the message from the transport layer into a raw
> SOAP message</p></td></tr></tbody></table></div>
-
-
-<p>You can determine the data format mode of an exchange by retrieving the
exchange property, <code>CamelCXFDataFormat</code>. The exchange key constant
is defined in
<code>org.apache.camel.component.cxf.CxfConstants.DATA_FORMAT_PROPERTY</code>.</p><h5
id="CXF-HowtoenableCXF'sLoggingOutInterceptorinMESSAGEmode">How to enable
CXF's LoggingOutInterceptor in MESSAGE mode</h5><p>CXF's
<code>LoggingOutInterceptor</code> outputs outbound message that goes on the
wire to logging system (Java Util Logging). Since the
<code>LoggingOutInterceptor</code> is in <code>PRE_STREAM</code> phase (but
<code>PRE_STREAM</code> phase is removed in <code>MESSAGE</code> mode), you
have to configure <code>LoggingOutInterceptor</code> to be run during the
<code>WRITE</code> phase. The following is an example.</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="CXF-Options">Options</h3><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Required</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>wsdlURL</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>The location of the WSDL. It is obtained
from endpoint address by default. <br clear="none" class="atl-forced-newline">
<br clear="none" class="atl-forced-newline"> <em>Example</em>: <a shape="rect"
class="external-link" href="file://local/wsdl/hello.wsdl"
rel="nofollow">file://local/wsdl/hello.wsdl</a> or
<code>wsdl/hello.wsdl</code></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>serviceClass</code></p></td><td colspan="1"
rowspan="1" class="
confluenceTd"><p>Yes</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>The name of the SEI (Service Endpoint Interface) class.
This class can have, but does not require, JSR181 annotations. <br clear="none"
class="atl-forced-newline"> This option is only required by POJO mode. If the
wsdlURL option is provided, serviceClass is not required for PAYLOAD and
MESSAGE mode. When wsdlURL option is used without serviceClass, the serviceName
and portName (endpointName for Spring configuration) options
<strong>MUST</strong> be provided. It is possible to use <code>#</code>
notation to reference a <code>serviceClass</code> object instance from the
registry. E.g. <code>serviceClass=#beanName</code>. The
<code>serviceClass</code> for a CXF producer (that is, the <code>to</code>
endpoint) should be a Java interface.<br clear="none"
class="atl-forced-newline"> <strong>Since 2.8,</strong> it is possible to omit
both wsdlURL and serviceClass options for PAYLOAD and MESSAGE mode. When they
are omitted, arbitrary XML elements can be put in CxfPayload's body in
PAYLOAD mode to facilitate CXF Dispatch Mode. <br clear="none"
class="atl-forced-newline"> <br clear="none" class="atl-forced-newline"> Please
be advised that the <strong>referenced object cannot be a Proxy</strong>
(Spring AOP Proxy is OK) as it relies on
<code>Object.getClass().getName()</code> method for non Spring AOP Proxy. <br
clear="none" class="atl-forced-newline"> <br clear="none"
class="atl-forced-newline"> <em>Example</em>:
<code>org.apache.camel.Hello</code></p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>serviceName</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>The service name this service is
implementing, it maps to the <code>wsdl:service@name</code>. <br clear="none"
class="atl-forced-newline"> <br clear="none" class="atl-forced-newline">
<strong>Required</strong> for camel-cxf consumer
since camel-2.2.0 or if more than one <code>serviceName</code> is present in
WSDL. <br clear="none" class="atl-forced-newline"> <br clear="none"
class="atl-forced-newline"> <em>Example</em>:
{http:­//org.apache.camel}ServiceName</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>endpointName</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>The port name this service is implementing,
it maps to the <code>wsdl:port@name</code>. <br clear="none"
class="atl-forced-newline"> <br clear="none" class="atl-forced-newline">
<strong>Required</strong> for camel-cxf consumer since camel-2.2.0 or if more
than one <code>portName</code> is present under <code>serviceName</code>. <br
clear="none" class="atl-forced-newline"> <br clear="none"
class="atl-forced-newline"> <em>Example</em>:
{http:­//org.apache.camel}PortName</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><
p><code>dataFormat</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>No</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>The data type messages supported by the CXF endpoint.
<br clear="none" class="atl-forced-newline"> <br clear="none"
class="atl-forced-newline"> <em>Default</em>: <code>POJO</code> <br
clear="none" class="atl-forced-newline"> <em>Example</em>: <code>POJO</code>,
<code>PAYLOAD</code>, <code>MESSAGE</code></p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>relayHeaders</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Please see the <strong>Description
of</strong> <code><strong>relayHeaders</strong></code> <strong>option</strong>
section for this option. Should a CXF endpoint relay headers along the route.
Currently only available when <code>dataFormat=POJO</code> <br clear="none"
class="atl-forced-newline"> <br clear="none" class="atl-f
orced-newline"> <em>Default</em>: <code>true</code> <br clear="none"
class="atl-forced-newline"> <em>Example</em>: <code>true</code>,
<code>false</code></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>wrapped</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Which kind of operation that CXF endpoint producer will
invoke <br clear="none" class="atl-forced-newline"> <br clear="none"
class="atl-forced-newline"> <em>Default</em>: <code>false</code> <br
clear="none" class="atl-forced-newline"> <em>Example</em>: <code>true</code>,
<code>false</code></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>wrappedStyle</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><strong>New in 2.5.0</strong> The WSDL style that
describes how parameters are represented in the SOAP body. If the value
is false, CXF will chose the document-literal unwrapped style, If the value is
true, CXF will chose the document-literal wrapped style <br clear="none"
class="atl-forced-newline"> <br clear="none" class="atl-forced-newline">
<em>Default</em>: <code>Null</code> <br clear="none"
class="atl-forced-newline"> <em>Example</em>: <code>true</code>,
<code>false</code></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>setDefaultBus</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Will set the default bus when CXF endpoint create a bus
by itself <br clear="none" class="atl-forced-newline"> <br clear="none"
class="atl-forced-newline"> <em>Default</em>: <code>false</code> <br
clear="none" class="atl-forced-newline"> <em>Example</em>: <code>true</code>,
<code>false</code></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>bus</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>No</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>A default bus created by CXF Bus Factory. Use
<code>#</code> notation to reference a bus object from the registry. The
referenced object must be an instance of <code>org.apache.cxf.Bus</code>. <br
clear="none" class="atl-forced-newline"> <br clear="none"
class="atl-forced-newline"> <em>Example</em>:
<code>bus=#busName</code></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>cxfBinding</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Use <code>#</code> notation to reference a CXF binding
object from the registry. The referenced object must be an instance of
<code>org.apache.camel.component.cxf.CxfBinding</code> (use an instance of
<code>org.apache.camel.component.cxf.DefaultCxfBinding</code>). <br
clear="none" class="atl-forced-newline"> <br clear="none"
class="atl-forced-newline"> <em>Example<
/em>: <code>cxfBinding=#bindingName</code></p></td></tr><tr><td colspan="1"
rowspan="1"
class="confluenceTd"><p><code>headerFilterStrategy</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Use <code>#</code> notation to reference a
header filter strategy object from the registry. The referenced object must be
an instance of <code>org.apache.camel.spi.HeaderFilterStrategy</code> (use an
instance of
<code>org.apache.camel.component.cxf.CxfHeaderFilterStrategy</code>). <br
clear="none" class="atl-forced-newline"> <br clear="none"
class="atl-forced-newline"> <em>Example</em>:
<code>headerFilterStrategy=#strategyName</code></p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>loggingFeatureEnabled</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>New in 2.3. This option enables CXF Logging
Feature which write
s inbound and outbound SOAP messages to log. <br clear="none"
class="atl-forced-newline"> <br clear="none" class="atl-forced-newline">
<em>Default</em>: <code>false</code> <br clear="none"
class="atl-forced-newline"> <em>Example</em>:
<code>loggingFeatureEnabled</code><code>=true</code></p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>defaultOperationName</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>New in 2.4, this option will set the
default operationName that will be used by the CxfProducer which invokes the
remote service. <br clear="none" class="atl-forced-newline"> <br clear="none"
class="atl-forced-newline"> <em>Default</em>: <code>null</code> <br
clear="none" class="atl-forced-newline"> <em>Example</em>:
<code>defaultOperationName</code><code>=greetMe</code></p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>defaultOperationNamespace</code></
p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>No</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>New in 2.4. This option will
set the default operationNamespace that will be used by the CxfProducer which
invokes the remote service. <br clear="none" class="atl-forced-newline"> <br
clear="none" class="atl-forced-newline"> <em>Default</em>: <code>null</code>
<br clear="none" class="atl-forced-newline"> <em>Example</em>:
<code>defaultOperationNamespace</code><code>=</code><code><a shape="rect"
class="external-link"
href="http://apache.org/hello_world_soap_http";>http://apache.org/hello_world_soap_http</a></code></p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>synchronous</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>New in 2.5. This option will let cxf endpoint decide to
use sync or async API to do the underlying work. The default value is false
which me
ans camel-cxf endpoint will try to use async API by default. <br clear="none"
class="atl-forced-newline"> <br clear="none" class="atl-forced-newline">
<em>Default</em>: <code>false</code> <br clear="none"
class="atl-forced-newline"> <em>Example</em>:
synchronous=true</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>publishedEndpointUrl</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>New in 2.5. This option can override the
endpointUrl that published from the WSDL which can be accessed with service
address url plus ?wsdl. <br clear="none" class="atl-forced-newline"> <br
clear="none" class="atl-forced-newline"> <em>Default</em>: <code>null</code>
<br clear="none" class="atl-forced-newline"> <em>Example</em>:
publshedEndpointUrl=<a shape="rect" class="external-link"
href="http://example.com/service";
rel="nofollow">http://example.com/service</a></p></td></tr><tr><td colspan="1"
ro
wspan="1" class="confluenceTd"><p><code>properties.XXX</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><strong>Camel 2.8:</strong> Allows to set
custom properties to CXF in the endpoint uri. For example setting
<code>properties.mtom-enabled=true</code> to enable MTOM.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>allowStreaming</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>New in 2.8.2. This option controls whether the CXF
component, when running in PAYLOAD mode (see below), will DOM parse the
incoming messages into DOM Elements or keep the payload as a
javax.xml.transform.Source object that would allow streaming in some
cases.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>skipFaultLogging</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>No</p><
/td><td colspan="1" rowspan="1" class="confluenceTd"><p>New in 2.11. This
option controls whether the PhaseInterceptorChain skips logging the Fault that
it catches.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>username</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>New in <strong>Camel 2.12.3</strong> This option is
used to set the basic authentication information of username for the CXF
client.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>password</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>New in <strong>Camel 2.12.3</strong> This option is
used to set the basic authentication information of password for the CXF
client.</p></td></tr></tbody></table></div><p>The <code>serviceName</code> and
<code>portName</code> are <a shape="rect" class="external-link" hre
f="http://en.wikipedia.org/wiki/QName"; rel="nofollow">QNames</a>, so if you
provide them be sure to prefix them with their {namespace} as shown in the
examples above.</p><h4 id="CXF-Thedescriptionsofthedataformats">The
descriptions of the dataformats</h4><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>DataFormat</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>POJO</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>POJOs (Plain old Java objects) are the Java
parameters to the method being invoked on the target server. Both Protocol and
Logical JAX-WS handlers are supported.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>PAYLOAD</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><code>PAYLOAD</code> is the
message payload (the contents of the <code>soap:body</
code>) after message configuration in the CXF endpoint is applied. Only
Protocol JAX-WS handler is supported. Logical JAX-WS handler is not
supported.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>MESSAGE</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>MESSAGE</code> is the raw message
that is received from the transport layer. It is not suppose to touch or change
Stream, some of the CXF interceptor will be removed if you are using this kind
of DataFormat so you can't see any soap headers after the camel-cxf consumer
and JAX-WS handler is not supported.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>CXF_MESSAGE</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>New in <strong>Camel
2.8.2</strong>, <code>CXF_MESSAGE</code> allows for invoking the full
capabilities of CXF interceptors by converting the message from the transport
layer into a raw SOAP message</p></td></tr></tbody></table><
/div><p>You can determine the data format mode of an exchange by retrieving
the exchange property, <code>CamelCXFDataFormat</code>. The exchange key
constant is defined in
<code>org.apache.camel.component.cxf.CxfConstants.DATA_FORMAT_PROPERTY</code>.</p><h5
id="CXF-HowtoenableCXF'sLoggingOutInterceptorinMESSAGEmode">How to enable
CXF's LoggingOutInterceptor in MESSAGE mode</h5><p>CXF's
<code>LoggingOutInterceptor</code> outputs outbound message that goes on the
wire to logging system (Java Util Logging). Since the
<code>LoggingOutInterceptor</code> is in <code>PRE_STREAM</code> phase (but
<code>PRE_STREAM</code> phase is removed in <code>MESSAGE</code> mode), you
have to configure <code>LoggingOutInterceptor</code> to be run during the
<code>WRITE</code> phase. The following is an example.</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
<bean id="loggingOutInterceptor"
class="org.apache.cxf.interceptor.LoggingOutInterceptor">
<!-- it really should have been user-prestream but CXF does have
such phase! -->
@@ -207,15 +196,8 @@ div.rbtoc1395408039545 li {margin-left:
</property>
</bean>
]]></script>
-</div></div></li><li><p>Other than <code>relayHeaders</code>, there are new
properties that can be configured in
<code>CxfHeaderFilterStrategy</code>.</p><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p> Required </p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>relayHeaders</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> No </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> All message headers will be processed by
Message Header Filters <br clear="none" class="atl-forced-newline"> <br
clear="none" class="atl-forced-newline"> <em>Type</em>: <code>boolean</code>
<br clear="none" class="atl-forced-newline"> <em>Default</em>:
<code>true</code> </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>re
layAllMessageHeaders</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> No </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> All message headers will be propagated (without
processing by Message Header Filters) <br clear="none"
class="atl-forced-newline"> <br clear="none" class="atl-forced-newline">
<em>Type</em>: <code>boolean</code> <br clear="none"
class="atl-forced-newline"> <em>Default</em>: <code>false</code>
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>allowFilterNamespaceClash</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> No </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> If two filters overlap in activation namespace, the
property control how it should be handled. If the value is <code>true</code>,
last one wins. If the value is <code>false</code>, it will throw an exception
<br clear="none" class="atl-forced-newline"> <br clear="none"
class="atl-forced-newline"> <em>Type</e
m>: <code>boolean</code> <br clear="none" class="atl-forced-newline">
<em>Default</em>: <code>false</code> </p></td></tr></tbody></table></div>
-
-
-<h3 id="CXF-ConfiguretheCXFendpointswithSpring">Configure the CXF endpoints
with Spring</h3>
-
-<p>You can configure the CXF endpoint with the Spring configuration file shown
below, and you can also embed the endpoint into the <code>camelContext</code>
tags. When you are invoking the service endpoint, you can set the
<code>operationName</code> and <code>operationNamespace</code> headers to
explicitly state which operation you are calling.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[
-<beans xmlns="http://www.springframework.org/schema/beans"
+</div></div></li><li><p>Other than <code>relayHeaders</code>, there are new
properties that can be configured in
<code>CxfHeaderFilterStrategy</code>.</p><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Required</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>relayHeaders</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>All message headers will be processed by
Message Header Filters <br clear="none" class="atl-forced-newline"> <br
clear="none" class="atl-forced-newline"> <em>Type</em>: <code>boolean</code>
<br clear="none" class="atl-forced-newline"> <em>Default</em>:
<code>true</code></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>relayAllMessage
Headers</code></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>No</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>All message headers will be propagated (without
processing by Message Header Filters) <br clear="none"
class="atl-forced-newline"> <br clear="none" class="atl-forced-newline">
<em>Type</em>: <code>boolean</code> <br clear="none"
class="atl-forced-newline"> <em>Default</em>:
<code>false</code></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>allowFilterNamespaceClash</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>No</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>If two filters overlap in activation
namespace, the property control how it should be handled. If the value is
<code>true</code>, last one wins. If the value is <code>false</code>, it will
throw an exception <br clear="none" class="atl-forced-newline"> <br
clear="none" class="atl-forced-newline"> <em>Type</em>: <code>boolean</code>
<br clear="none" class="atl-forced-newline"> <em>Default</em>:
<code>false</code></p></td></tr></tbody></table></div><h3
id="CXF-ConfiguretheCXFendpointswithSpring">Configure the CXF endpoints with
Spring</h3><p>You can configure the CXF endpoint with the Spring configuration
file shown below, and you can also embed the endpoint into the
<code>camelContext</code> tags. When you are invoking the service endpoint, you
can set the <code>operationName</code> and <code>operationNamespace</code>
headers to explicitly state which operation you are calling.</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><![CDATA[<beans
xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:cxf="http://camel.apache.org/schema/cxf"
xsi:schemaLocation="
@@ -238,19 +220,7 @@ div.rbtoc1395408039545 li {margin-left:
</camelContext>
</beans>
]]></script>
-</div></div>
-
-<p>Be sure to include the JAX-WS <code>schemaLocation</code> attribute
specified on the root beans element. This allows CXF to validate the file and
is required. Also note the namespace declarations at the end of the
<code><cxf:cxfEndpoint/></code> tag--these are required because the
combined {<code>namespace}localName</code> syntax is presently not supported
for this tag's attribute values.</p>
-
-<p>The <code>cxf:cxfEndpoint</code> element supports many additional
attributes:</p>
-
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p> Value </p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>PortName</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> The endpoint name this service
is implementing, it maps to the <code>wsdl:port@name</code>. In the format of
<code>ns:PORT_NAME</code> where <code>ns</code> is a namespace prefix valid at
this scope. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>serviceName</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> The service name this service is
implementing, it maps to the <code>wsdl:service@name</code>. In the format of
<code>ns:SERVICE_NAME</code> where <code>ns</code> is a namespace prefix valid
at this scope. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>wsdlURL</c
ode> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The
location of the WSDL. Can be on the classpath, file system, or be hosted
remotely. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>bindingId</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> The <code>bindingId</code> for the service
model to use. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>address</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> The service publish address.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>bus</code> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
The bus name that will be used in the JAX-WS endpoint. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>serviceClass</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The class name of
the SEI (Service Endpoint Interface) class which could have JSR18
1 annotation or not. </p></td></tr></tbody></table></div>
-
-
-<p>It also supports many child elements:</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p> Value </p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>cxf:inInterceptors</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The incoming
interceptors for this endpoint. A list of <code><bean></code> or
<code><ref></code>. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>cxf:inFaultInterceptors</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> The incoming fault
interceptors for this endpoint. A list of <code><bean></code> or
<code><ref></code>. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>cxf:outInterceptors</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> The outgoing interceptors for
this endpoint. A list of <code><bean></co
de> or <code><ref></code>. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>cxf:outFaultInterceptors</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> The outgoing fault
interceptors for this endpoint. A list of <code><bean></code> or
<code><ref></code>. </p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p> <code>cxf:properties</code> </p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p> A properties map which should be supplied
to the JAX-WS endpoint. See below. </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>cxf:handlers</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> A JAX-WS handler list which
should be supplied to the JAX-WS endpoint. See below. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> <code>cxf:dataBinding</code>
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> You can specify
the which <code>Data
Binding</code> will be use in the endpoint. This can be supplied using the
Spring <code><bean class="MyDataBinding"/></code> syntax.
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>cxf:binding</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> You can specify the <code>BindingFactory</code> for
this endpoint to use. This can be supplied using the Spring <code><bean
class="MyBindingFactory"/></code> syntax. </p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p> <code>cxf:features</code> </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> The features that hold the
interceptors for this endpoint. A list of {{<bean>}}s or {{<ref>}}s
</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>cxf:schemaLocations</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> The schema locations for endpoint to use. A list of
{{<schemaLocation>}}s </p></td></tr><
tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
<code>cxf:serviceFactory</code> </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> The service factory for this endpoint to use. This can
be supplied using the Spring <code><bean
class="MyServiceFactory"/></code> syntax </p></td></tr></tbody></table></div>
-
-<div></div></li></ul><p>You can find more advanced examples which show how to
provide interceptors , properties and handlers here:<br clear="none"> <a
shape="rect" class="external-link"
href="http://cwiki.apache.org/CXF20DOC/jax-ws-configuration.html";>http://cwiki.apache.org/CXF20DOC/jax-ws-configuration.html</a></p><p><strong>NOTE</strong><br
clear="none"> You can use cxf:properties to set the camel-cxf endpoint's
dataFormat and setDefaultBus properties from spring configuration file.</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+</div></div><p>Be sure to include the JAX-WS <code>schemaLocation</code>
attribute specified on the root beans element. This allows CXF to validate the
file and is required. Also note the namespace declarations at the end of the
<code><cxf:cxfEndpoint/></code> tag--these are required because the
combined {<code>namespace}localName</code> syntax is presently not supported
for this tag's attribute values.</p><p>The <code>cxf:cxfEndpoint</code> element
supports many additional attributes:</p><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>PortName</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>The endpoint name this service is
implementing, it maps to the <code>wsdl:port@name</code>. In the format of
<code>ns:PORT_NAME</code> where <code>ns</code>
is a namespace prefix valid at this scope.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>serviceName</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The service name this service
is implementing, it maps to the <code>wsdl:service@name</code>. In the format
of <code>ns:SERVICE_NAME</code> where <code>ns</code> is a namespace prefix
valid at this scope.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>wsdlURL</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>The location of the WSDL. Can be on the
classpath, file system, or be hosted remotely.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>bindingId</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The <code>bindingId</code> for
the service model to use.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>address</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p
>The service publish address.</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>bus</code></p></td><td colspan="1" rowspan="1"
>class="confluenceTd"><p>The bus name that will be used in the JAX-WS
>endpoint.</p></td></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>serviceClass</code></p></td><td colspan="1"
>rowspan="1" class="confluenceTd"><p>The class name of the SEI (Service
>Endpoint Interface) class which could have JSR181 annotation or
>not.</p></td></tr></tbody></table></div><p>It also supports many child
>elements:</p><div class="table-wrap"><table
>class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
>class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1"
>class="confluenceTh"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"
>class="confluenceTd"><p><code>cxf:inInterceptors</code></p></td><td
>colspan="1" rowspan="1" class="confluenceTd"><p>The incoming interceptors for
>this endpoint. A list of <code><bean></cod
e> or <code><ref></code>.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>cxf:inFaultInterceptors</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The incoming fault interceptors
for this endpoint. A list of <code><bean></code> or
<code><ref></code>.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>cxf:outInterceptors</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The outgoing interceptors for
this endpoint. A list of <code><bean></code> or
<code><ref></code>.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>cxf:outFaultInterceptors</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The outgoing fault interceptors
for this endpoint. A list of <code><bean></code> or
<code><ref></code>.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>cxf:properties</code></p></td><td colspan="1"
rowspan
="1" class="confluenceTd"><p>A properties map which should be supplied to the
JAX-WS endpoint. See below.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>cxf:handlers</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>A JAX-WS handler list which should be
supplied to the JAX-WS endpoint. See below.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>cxf:dataBinding</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>You can specify the which
<code>DataBinding</code> will be use in the endpoint. This can be supplied
using the Spring <code><bean class="MyDataBinding"/></code>
syntax.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>cxf:binding</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>You can specify the
<code>BindingFactory</code> for this endpoint to use. This can be supplied
using the Spring <code><bean class="MyBindingFactory"/></code> syn
tax.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>cxf:features</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>The features that hold the interceptors for
this endpoint. A list of {{<bean>}}s or
{{<ref>}}s</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>cxf:schemaLocations</code></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>The schema locations for
endpoint to use. A list of {{<schemaLocation>}}s</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>cxf:serviceFactory</code></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>The service factory for this endpoint to
use. This can be supplied using the Spring <code><bean
class="MyServiceFactory"/></code>
syntax</p></td></tr></tbody></table></div><div></div></li></ul><p>You can find
more advanced examples which show how to provide interceptors , properties and
handlers here:<br clear="none"> <
a shape="rect" class="external-link"
href="http://cwiki.apache.org/CXF20DOC/jax-ws-configuration.html";>http://cwiki.apache.org/CXF20DOC/jax-ws-configuration.html</a></p><p><strong>NOTE</strong><br
clear="none"> You can use cxf:properties to set the camel-cxf endpoint's
dataFormat and setDefaultBus properties from spring configuration file.</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
<script class="theme: Default; brush: xml; gutter: false"
type="syntaxhighlighter"><