svn commit: r882373 - in /websites/production/cxf/content: cache/docs.pageCache docs/ws-reliablemessaging.html

[bu...@apache.org]

Author: buildbot
Date: Sun Oct 13 07:48:39 2013
New Revision: 882373

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 07:48:39 2013
@@ -122,7 +122,7 @@ 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 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>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 http://docs.oasis-open.org/ws-rx/wsrm/200702 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 http://schemas.xmlsoap.org/ws/2005/02/rm/ 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>
 
@@ -141,7 +141,28 @@ Apache CXF -- WS-ReliableMessaging
 
 <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>
+<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>
+
+<h2><a shape="rect" name="WS-ReliableMessaging-Runtimecontrol"></a>Runtime control</h2>
+
+<p>Several message context property values can be set in client code to control the RM operation at runtime, with key values defined by public constants in org.apache.cxf.ws.rm.RMManager:</p>
+
+<div class="table-wrap">
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Key </th><th colspan="1" rowspan="1" class="confluenceTh"> Value </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> WSRM_VERSION_PROPERTY </td><td colspan="1" rowspan="1" class="confluenceTd"> String WS-RM version namespace (
+<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>
+<p> or </p>
+<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>
+<p>) </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> WSRM_WSA_VERSION_PROPERTY </td><td colspan="1" rowspan="1" class="confluenceTd"> String WS-Addressing version namespace (
+<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>
+<p> or </p>
+<a shape="rect" class="external-link" href="http://www.w3.org/2005/08/addressing" rel="nofollow">http://www.w3.org/2005/08/addressing</a>
+<p>) - this property is ignored unless you're using the </p>
+<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>
+<p> RM namespace) </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> WSRM_LAST_MESSAGE_PROPERTY </td><td colspan="1" rowspan="1" class="confluenceTd"> Boolean value TRUE to tell the RM code that the last message is being sent, allowing the code to close the RM sequence and release resources (as of the 3.0.0 version of CXF the RM code will by default close the RM sequence when you close your client; earlier versions of CXF did not close the sequence unless told to using this flag, or if configured with a source policy &lt;wsrm-mgr:sequenceTerminationPolicy terminateOnShutdown="true"/&gt;) </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> WSRM_INACTIVITY_TIMEOUT_PROPERTY </td><td colspan="1" rowspan="1" class="confluenceTd"> Long inactivity timeout in milliseconds </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> WSRM_RETRANSMISSION_INTERVAL_PROPERTY </td><td colspan="1" rowspan="1" class="confluenceTd"> Long base retransmission interval in
  milliseconds </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> WSRM_EXPONENTIAL_BACKOFF_PROPERTY </td><td colspan="1" rowspan="1" class="confluenceTd"> Boolean exponential backoff flag </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> WSRM_ACKNOWLEDGEMENT_INTERVAL_PROPERTY </td><td colspan="1" rowspan="1" class="confluenceTd"> Long acknowledgement interval in milliseconds </td></tr></tbody></table>
+</div>
+
+
+<p>You can also monitor and control many aspects of RM using the JMX+Management features of CXF. </p></div>
            </div>
            <!-- Content -->
          </td>