[ws-rx] i021; proposal around option 3

["Gilbert Pilz" <Gilbert.Pilz@bea.com>]

Title: [ws-rx] i021; proposal around option 3

Issue: http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml#i021

This proposal addresses the issue by splitting the current <wsrmp:RMAssertion> into two separate assertions:

<wsrmp:RMInbound [wsp:Optional="true"]? ... >
    <wsrmp:AcknowledgementInterval Milliseconds="xs:unsignedLong" ... /> ?
    <wsrmp:MaxMessageNumber Number="xs:unsignedLong" ... /> ?
    ...
</wsrm:RMInbound>

and

<wsrmp:RMOutbound [wsp:Optional="true"]? ...>
    ...
</wsrmp:RMOutbound>

Note that <wsrmp:RMInbound> preserves the configuration parameters currently contained in <wsrmp:RMAssertion>.

To indicate that RM is required for inbound messages only you might use something like the following policy (note: same as current example in WS-RM Policy)

<wsp:Policy wsu:Id="MyPolicy" >
    <wsp:ExactlyOne>
        <wsrmp:RMInbound>
            <wsrmp:AcknowledgementInterval Milliseconds="200" />
        </wsrmp:RMInbound>
    </wsp:ExactlyOne>
</wsp:Policy>

Note this proposal does not change the current specification with regards to supported policy attachment options (Endpoint Policy Subject; wsdl:binding or wsdl:port).

To indicate that RM is required for both inbound and outbound messages you might use something like the following policy:

<wsp:Policy wsu:Id="MyPolicy" >
    <wsp:ExactlyOne>
        <wsrmp:RMInbound>
            <wsrmp:AcknowledgementInterval Milliseconds="200" />
        </wsrmp:RMInbound>
        <wsrmp:RMOutbound />
    </wsp:ExactlyOne>
</wsp:Policy>

Obviously you can use combinations of these assertions and the wsp:Optional attribute to indicate many different policy combinations such as:

• an endpoint requires RM for inbound messages and supports the optional use of RM for outbound messages
• an endpoint does not support RM for inbound messages but requires the use of RM for outbound messages
• etc.