Author: buildbot
Date: Sun Oct 13 06:48:03 2013
New Revision: 882368
Log:
Production update by buildbot for cxf
Modified:
websites/production/cxf/content/cache/docs.pageCache
websites/production/cxf/content/docs/ws-reliablemessaging.html
Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/cxf/content/docs/ws-reliablemessaging.html
==============================================================================
--- websites/production/cxf/content/docs/ws-reliablemessaging.html (original)
+++ websites/production/cxf/content/docs/ws-reliablemessaging.html Sun Oct 13
06:48:03 2013
@@ -122,11 +122,16 @@ Apache CXF -- WS-ReliableMessaging
<div class="wiki-content">
<div id="ConfluenceContent"><h1><a shape="rect"
name="WS-ReliableMessaging-WSReliableMessaging"></a>WS-Reliable Messaging</h1>
-<p>CXF supports the February 2005 version of the <a shape="rect"
class="external-link" href="http://schemas.xmlsoap.org/ws/2005/02/rm/";
rel="nofollow">Web Services Reliable Messaging</a> Protocol
(WS-ReliableMessaging) specification. Like most other features in CXF, it is
interceptor based. <br clear="none">
-The WS-Reliable Messaging implementation consists of 4 interceptors in
total:</p>
+<p>CXF supports both the official <a shape="rect" class="external-link"
href="http://docs.oasis-open.org/ws-rx/wsrm/200702"; rel="nofollow">1.1/1.2 Web
Services Reliable Messaging</a> (WS-ReliableMessaging) protocol using the <a
shape="rect" class="external-link"
href="http://docs.oasis-open.org/ws-rx/wsrm/200702";
rel="nofollow">http://docs.oasis-open.org/ws-rx/wsrm/200702</a> namespace and
the outdated <a shape="rect" class="external-link"
href="http://schemas.xmlsoap.org/ws/2005/02/rm/"; rel="nofollow">February 2005
submission version</a> using the <a shape="rect" class="external-link"
href="http://schemas.xmlsoap.org/ws/2005/02/rm/";
rel="nofollow">http://schemas.xmlsoap.org/ws/2005/02/rm/</a> namespace.</p>
+
+<p>The submission version specified an outdated version of WS-Addressing,
using the <a shape="rect" class="external-link"
href="http://schemas.xmlsoap.org/ws/2004/08/addressing";
rel="nofollow">http://schemas.xmlsoap.org/ws/2004/08/addressing</a> namespace,
which has since been replaced by the official <a shape="rect"
class="external-link" href="http://www.w3.org/2005/08/addressing";
rel="nofollow">http://www.w3.org/2005/08/addressing</a> namespace. Most other
web services implementations supporting the submission version of
WS-ReliableMessaging have deviated from the specification by moving to the
official WS-Addressing release with the <a shape="rect" class="external-link"
href="http://www.w3.org/2005/08/addressing";
rel="nofollow">http://www.w3.org/2005/08/addressing</a> namespace. CXF supports
the submission version of RM with either WS-Addressing namespace.</p>
+
+<p>For compatibility with older versions of CXF, the default is to use the
February 2005 submission version of RM with the submission version of
WS-Addressing. On the client side, you can CXF for whichever version of
WS-ReliableMessaging you want to use (see <a shape="rect"
href="wsrmconfiguration.html" title="WSRMConfiguration">Reliable Messaging
Configuration Guide</a>). On the provider side, CXF adapts to whichever version
of WS-ReliableMessaging is used by the client and responds appropriately.</p>
+
+<p>Like most other features in CXF, it is interceptor based. The WS-Reliable
Messaging implementation consists of 6 interceptors in total:</p>
<div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Interceptor </th><th colspan="1" rowspan="1"
class="confluenceTh"> Task </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> org.apache.cxf.ws.rm.RMOutInterceptor </td><td
colspan="1" rowspan="1" class="confluenceTd"> Responsible for sending
CreateSequence requests and waiting for their CreateSequenceResponse responses,
and and aggregating the sequence properties (id and message number) for an
application message.</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> org.apache.cxf.ws.rm.RMInInterceptor </td><td colspan="1"
rowspan="1" class="confluenceTd"> Intercepting and processing RM protocol
messages (these will not the application level), as well as
SequenceAcknowledgments piggybacked on application messages. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">
org.apache.cxf.ws.rm.RMCaptureInInterceptor </td><td colspan="1" rowspan="1"
class="confluenceTd
"> Caching messages for later retransmission. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> org.apache.cxf.ws.rm.RMDeliveryInterceptor
</td><td colspan="1" rowspan="1" class="confluenceTd"> Assuring InOrder
delivery of messages to the application. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> org.apache.cxf.ws.rm.soap.RMSoapInterceptor
</td><td colspan="1" rowspan="1" class="confluenceTd"> Encoding and decoding
the RM headers </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
org.apache.cxf.ws.rm.soap.RetransmissionInterceptor </td><td colspan="1"
rowspan="1" class="confluenceTd"> Responsible for creating copies of
application messages for future resends. </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Interceptor </th><th colspan="1" rowspan="1"
class="confluenceTh"> Task </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> org.apache.cxf.ws.rm.RMOutInterceptor </td><td
colspan="1" rowspan="1" class="confluenceTd"> Responsible for sending
CreateSequence requests and waiting for their CreateSequenceResponse responses,
and and aggregating the sequence properties (id and message number) for an
application message. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> org.apache.cxf.ws.rm.RMInInterceptor </td><td colspan="1"
rowspan="1" class="confluenceTd"> Intercepting and processing RM protocol
messages (these will not the application level), as well as
SequenceAcknowledgments piggybacked on application messages. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">
org.apache.cxf.ws.rm.RMCaptureInInterceptor </td><td colspan="1" rowspan="1"
class="confluenceT
d"> Caching messages for later retransmission. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> org.apache.cxf.ws.rm.RMDeliveryInterceptor
</td><td colspan="1" rowspan="1" class="confluenceTd"> Assuring InOrder
delivery of messages to the application. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> org.apache.cxf.ws.rm.soap.RMSoapInterceptor
</td><td colspan="1" rowspan="1" class="confluenceTd"> Encoding and decoding
the RM headers </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
org.apache.cxf.ws.rm.soap.RetransmissionInterceptor </td><td colspan="1"
rowspan="1" class="confluenceTd"> Responsible for creating copies of
application messages for future resends. </td></tr></tbody></table>
</div>
@@ -134,7 +139,7 @@ The WS-Reliable Messaging implementation
<p>The presence of the RM interceptors on the respective interceptor chains
alone will take care that RM protocol messages are exchanged when necessary.
For example, upon intercepting the first application message on the outbound
interceptor chain, the RMOutInterceptor will send a CreateSequence request and
only proceed with processing the original application message after it has the
CreateSequenceResponse response. Furthermore, the RM interceptors are
responsible for adding the Sequence headers to the application messages and, on
the destination side, extracting them from the message.</p>
-<p>This means that no changes to application code are required to make the
message exchange reliable! </p>
+<p>This means that no changes to application code are required to make the
message exchange reliable!</p>
<p>You can still control sequence demarcation and other aspects of the
reliable exchange through configuration however. For example, while CXF by
default attempts to maximize the lifetime of a sequence, thus reducing the
overhead incurred by the RM protocol messages, you can enforce the use of a
separate sequence per application message by configuring the RM source's
sequence termination policy (setting the maximum sequence length to 1). See the
<a shape="rect" href="wsrmconfiguration.html"
title="WSRMConfiguration">Reliable Messaging Configuration Guide</a> for more
details on configuring this and other aspects of the reliable
exchange.</p></div>
</div>
