Chapter 7.  Using WS-Reliable Messaging

In order for JBoss WS-CXF/CXF to establish reliable messaging between two points, the CXF RM and addressing interceptors need to be added to the interceptor chains. This can be achieved in one of the ways outlined below.
Using the RMAssertion and the CXF WS-Policy Framework

The RM interceptors will be automatically added to their respective interceptor chains by the policy framework if the following occurs:

  1. A Policy with an RMAssertion element is attached to the wsdl:service element (or any other WSDL element that is an attachment point for Policy or PolicyReference elements according to the rules for WS-Policy Attachments).
  2. The CXF WS-Policy Framework is enabled
The assertion attributes control the behavior of the source or destination. For example, to enable the WS-Policy Framework on the server side, your configuration file will look like this:
<jaxws:endpoint ...>
Your WSDL will look like this:
<wsp:Policy wsu:Id="RM" xmlns:wsp=""
    <wsam:Addressing xmlns:wsam="">
    <wsrmp:RMAssertion xmlns:wsrmp="">
        <wsrmp:BaseRetransmissionInterval Milliseconds="10000"/> 
<wsdl:service name="ReliableGreeterService">
    <wsdl:port binding="tns:GreeterSOAPBinding" name="GreeterPort">
        <soap:address location="http://localhost:9020/SoapContext/GreeterPort"/>
        <wsp:PolicyReference URI="#RM" xmlns:wsp=""/>        
Instead of attaching the PolicyReference to the wsdl:port element, you can also specify it as a child element of the policies featured, such as the server endpoint.
<wsp:Policy wsu:Id="="RM" xmlns:wsp="" ...>

<jaxws:endpoint ...>
	  <wsp:PolicyReference URI="#RM" xmlns:wsp=""/>
Using the Reliable Messaging Feature

You can use the ReliableMessaging feature if you do not want to involve the WS-Policy Framework, or want to configure additional parameters such as the sequence termination policy or the persistent store. The supported child elements are listed below.

An element of type RMAssertion.
An element of type DeliveryAssuranceType that describes the delivery assurance that should apply (AtMostOnce, AtLeastOnce, InOrder).
An element of type SourcePolicyType that allows you to configure details of the RM source, such as whether an offer should always be included in a CreateSequence request, or the sequence termination policy.
An element of type DestinationPolicyType that allows you to configure details of the RM destination, such as whether inbound offers should be accepted.
The store to use (default: null). This must be an element of type jdbcStore (in the same namespace), or a bean or a reference to a bean that implements the RMStore interface.
The jbdcStore element type is described below.
The following example is applied at bus level.
                <wsrm-policy:BaseRetransmissionInterval Milliseconds="4000"/>           
                <wsrm-policy:AcknowledgementInterval Milliseconds="2000"/>          
                <wsrm-mgr:sequenceTerminationPolicy maxLength="5"/>                    
            <wsrm-mgr:destinationPolicy acceptOffers="false">            
               <ref bean="myStore"/>
Configuring the Reliable Messaging Store

To enable persistence, you must specify the object implementing the persistent store for RM. You can develop your own, or use the JDBC based store that comes with CXF (class You can configure the latter using a custom jdbcStore bean. The supported attributes are in the table below.

Table 7.1.  Attributes

Attribute name String Default
driverClassName String org.apache.derby.jdbc.EmbeddedDriver
userName String null
passWord String null
url String jdbc:derby:rmdb;create=true
Here is an example:
  <wsrm-mgr:jdbcStore id="myStore"
Configuring the Reliable Messaging Manager Manually

To configure properties of the RM Manager, you can use the RMManager element. It supports the same child elements as the ReliableMessaging feature element above. For example, without using features, you can determine that sequences should have a maximum length of five as follows:

<wsrm-mgr:rmManager xmlns:wsrm-mgr="">
        <wsrm-mgr:sequenceTerminationPolicy maxLength="5"/>