Author: buildbot
Date: Wed Jun 13 16:57:31 2018
New Revision: 1031155

Log:
Production update by buildbot for cxf

Modified:
    websites/production/cxf/content/cache/docs.pageCache
    websites/production/cxf/content/docs/ws-addressing.html

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

Modified: websites/production/cxf/content/docs/ws-addressing.html
==============================================================================
--- websites/production/cxf/content/docs/ws-addressing.html (original)
+++ websites/production/cxf/content/docs/ws-addressing.html Wed Jun 13 16:57:31 
2018
@@ -117,34 +117,22 @@ Apache CXF -- WS-Addressing
          <td height="100%">
            <!-- Content -->
            <div class="wiki-content">
-<div id="ConfluenceContent"><h1 
id="WS-Addressing-WS-AddressingviaXMLConfiguration/JavaAPI">WS-Addressing via 
XML Configuration/Java API</h1>
-
-<p>CXF provides support for the 2004-08 and 1.0 versions of WS-Addressing. </p>
-
-<p>To enable WS-Addressing you may enable the WSAddressingFeature on your 
service. If you wish to use XML to configure this, you may use the following 
syntax:</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;">
-&lt;jaxws:endpoint id="{your.service.namespace}YourPortName"&gt;
+<div id="ConfluenceContent"><h1 
id="WS-Addressing-WS-AddressingviaXMLConfiguration/JavaAPI">WS-Addressing via 
XML Configuration/Java API</h1><p>CXF provides support for the 2004-08 and 1.0 
versions of WS-Addressing.</p><p>To enable WS-Addressing you may enable the 
WSAddressingFeature on your service. If you wish to use XML to configure this, 
you may use the following syntax:</p><div class="code panel pdl" 
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="brush: java; gutter: false; theme: Default">&lt;jaxws:endpoint 
id="{your.service.namespace}YourPortName"&gt;
   &lt;jaxws:features&gt;
     &lt;wsa:addressing xmlns:wsa="http://cxf.apache.org/ws/addressing"/&gt;
   &lt;/jaxws:features&gt;
 &lt;/jaxws:endpoint&gt;
 </pre>
-</div></div>
-<p>You can also use the same exact syntax with a &lt;jaxws:client&gt;</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;">
-&lt;jaxws: client id="{your.service.namespace}YourPortName"&gt;
+</div></div><p>You can also use the same exact syntax with a 
&lt;jaxws:client&gt;</p><div class="code panel pdl" style="border-width: 
1px;"><div class="codeContent panelContent pdl">
+<pre class="brush: java; gutter: false; theme: Default">&lt;jaxws:client 
id="{your.service.namespace}YourPortName"&gt;
   &lt;jaxws:features&gt;
     &lt;wsa:addressing xmlns:wsa="http://cxf.apache.org/ws/addressing"/&gt;
   &lt;/jaxws:features&gt;
 &lt;/jaxws:client&gt;
 </pre>
-</div></div>
-<p> From an API point of view this looks 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;">
-import org.apache.cxf.jaxws.EndpointImpl;
+</div></div><p>From an API point of view this looks 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">import 
org.apache.cxf.jaxws.EndpointImpl;
 import org.apache.cxf.ws.addressing.WSAddressingFeature;
 
 MyServiceImpl implementor =  new MyServiceImpl()
@@ -152,11 +140,8 @@ EndpointImpl ep = (EndpointImpl) Endpoin
 ep.getFeatures().add(new WSAddressingFeature());
 ep.publish("http://some/address";);
 </pre>
-</div></div>
-<p>You can also use it with the ClientProxyFactoryBeans and ServerFactoryBeans 
(and their JAX-WS versions, namely JaxWsProxyFactoryBean and 
JaxWsServerFactoryBean):</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;">
-import org.apache.cxf.frontend.simple.ClientProxyFactoryBean;
+</div></div><p>You can also use it with the ClientProxyFactoryBeans and 
ServerFactoryBeans (and their JAX-WS versions, namely JaxWsProxyFactoryBean and 
JaxWsServerFactoryBean):</p><div class="code panel pdl" style="border-width: 
1px;"><div class="codeContent panelContent pdl">
+<pre class="brush: java; gutter: false; theme: Default">import 
org.apache.cxf.frontend.simple.ClientProxyFactoryBean;
 import org.apache.cxf.ws.addressing.WSAddressingFeature;
 
 ClientProxyFactoryBean factory = new ClientProxyFactoryBean();
@@ -165,51 +150,28 @@ factory.setAddress("http://acme.come/som
 factory.getFeatures().add(new WSAddressingFeature());
 MyService client = (MyService) factory.create();
 </pre>
-</div></div>
-
-<h1 id="WS-Addressing-EnablingWS-AddressingwithWS-Policy">Enabling 
WS-Addressing with WS-Policy</h1>
-<p>If you're using <a shape="rect" href="ws-policy.html">WS-Policy</a>, CXF 
can automatically set up WS-Addressing for you if you use the 
&lt;Addressing&gt; policy expression.</p>
-
-<h1 id="WS-Addressing-Decoupledresponses">Decoupled responses</h1>
-<p>By default, WS-Addressing using anonymous Reply-To addresses.   This means 
the request/response patterns are synchronous in nature and the response is 
sent back via the normal reply channel.   However, WS-Addressing allows for a 
decoupled endpoint to be used for receiving the response and CXF will then 
correlate it with the appropriate request.  There are a few ways for 
configuring the address on which CXF will listen for decoupled WS-Addressing 
responses.</p>
-
-<h3 id="WS-Addressing-HTTPConduitconfiguration">HTTP Conduit configuration</h3>
-<p>The HTTP Conduit's client configuration has an option for a 
DecoupledEndpoint address.  If the conduit has this configured, all requests 
sent via that conduit that have WS-Addressing enabled will have their responses 
sent to that endpoint:</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;">
-    &lt;http:conduit 
name="{http://apache.org/hello_world_soap_http}SoapPort.http-conduit"&gt;
-      &lt;http:client 
DecoupledEndpoint="http://localhost:9090/decoupled_endpoint"/&gt;
-    &lt;/http:conduit&gt;
+</div></div><h1 id="WS-Addressing-EnablingWS-AddressingwithWS-Policy">Enabling 
WS-Addressing with WS-Policy</h1><p>If you're using <a shape="rect" 
href="ws-policy.html">WS-Policy</a>, CXF can automatically set up WS-Addressing 
for you if you use the &lt;Addressing&gt; policy expression.</p><h1 
id="WS-Addressing-Decoupledresponses">Decoupled responses</h1><p>By default, 
WS-Addressing uses anonymous Reply-To addresses. This means the 
request/response patterns are synchronous in nature and the response is sent 
back via the normal reply channel. However, WS-Addressing allows for a 
decoupled endpoint to be used for receiving the response and CXF will then 
correlate it with the appropriate request. There are a few ways for configuring 
the address on which CXF will listen for decoupled WS-Addressing 
responses.</p><h3 id="WS-Addressing-HTTPConduitconfiguration">HTTP Conduit 
configuration</h3><p>The HTTP Conduit's client configuration has an option for 
a DecoupledEndpoint address. If the con
 duit has this configured, all requests sent via that conduit that have 
WS-Addressing enabled will have their responses sent to that endpoint:</p><div 
class="code panel pdl" style="border-width: 1px;"><div class="codeContent 
panelContent pdl">
+<pre class="brush: java; gutter: false; theme: Default">&lt;http:conduit 
name="{http://apache.org/hello_world_soap_http}SoapPort.http-conduit"&gt;
+    &lt;http:client 
DecoupledEndpoint="http://localhost:9090/decoupled_endpoint"/&gt;
+&lt;/http:conduit&gt;
 </pre>
-</div></div>
-
-<h3 id="WS-Addressing-RequestProperty">Request Property</h3>
-<p>The address can be set via a Request Context property.   </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;">
-((BindingProvider)proxy).getRequestContext()
+</div></div><h3 id="WS-Addressing-RequestProperty">Request Property</h3><p>The 
address can be set via a Request Context property.</p><div class="code panel 
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<pre class="brush: java; gutter: false; theme: 
Default">((BindingProvider)proxy).getRequestContext()
     .put("org.apache.cxf.ws.addressing.replyto", 
"http://localhost:9090/decoupled_endpoint";);
 </pre>
-</div></div>
-
-<h3 id="WS-Addressing-AddressingProperties">AddressingProperties</h3>
-<p>The CXF org.apache.cxf.ws.addressing.impl.AddressingPropertiesImpl object 
can be used to control many aspects of WS-Addressing including the Reply-To:</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;">
-        AddressingProperties maps = new AddressingPropertiesImpl();
-        EndpointReferenceType ref = new EndpointReferenceType();
-        AttributedURIType add = new AttributedURIType();
-        add.setValue("http://localhost:9090/decoupled_endpoint";);
-        ref.setAddress(add);
-        maps.setReplyTo(ref);
-        maps.setFaultTo(ref);
+</div></div><h3 
id="WS-Addressing-AddressingProperties">AddressingProperties</h3><p>The CXF 
org.apache.cxf.ws.addressing.impl.AddressingPropertiesImpl object can be used 
to control many aspects of WS-Addressing including the Reply-To:</p><div 
class="code panel pdl" style="border-width: 1px;"><div class="codeContent 
panelContent pdl">
+<pre class="brush: java; gutter: false; theme: Default">AddressingProperties 
maps = new AddressingPropertiesImpl();
+EndpointReferenceType ref = new EndpointReferenceType();
+AttributedURIType add = new AttributedURIType();
+add.setValue("http://localhost:9090/decoupled_endpoint";);
+ref.setAddress(add);
+maps.setReplyTo(ref);
+maps.setFaultTo(ref);
 
-        ((BindingProvider)port).getRequestContext()
-            .put("javax.xml.ws.addressing.context", maps);
+((BindingProvider)port).getRequestContext()
+        .put("javax.xml.ws.addressing.context", maps);
 </pre>
-</div></div>
-<div class="confluence-information-macro 
confluence-information-macro-note"><span class="aui-icon aui-icon-small 
aui-iconfont-warning confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><p>This method can also be used to 
configure the namespace/version of the WS-Addressing headers, exact message 
ID's, etc...</p></div></div></div>
+</div></div><div class="confluence-information-macro 
confluence-information-macro-note"><span class="aui-icon aui-icon-small 
aui-iconfont-warning confluence-information-macro-icon"></span><div 
class="confluence-information-macro-body"><p>This method can also be used to 
configure the namespace/version of the WS-Addressing headers, exact message 
ID's, etc...</p></div></div></div>
            </div>
            <!-- Content -->
          </td>


Reply via email to