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

Gil solution appears fine to me, but needs be more precise on what goes inside the RMOutbound assertion.

Two options:

(1) the two properties (AI and Max number) are only relevant to RMInbound, as they matter to the RMD. In that case RMOutbound is always empty, just indicating the need to use the RM protocol for outbound messages. However the client endpoint - acting as an RMD for received outbound messages - still need to get somewhere its own AI and MaxNumber values... ( that can be left out of scope here, could be in a policy/RMInbound that is not attached to any WSDL)

(2) the two properties (AI and Max number) although only relevant to RMD role, can be used in RMOutbound. In that case they represent some recommended/expected values for the client endpoint to use on its RMD.

I'd prefer (1).

Jacques

From: Gilbert Pilz [mailto:Gilbert.Pilz@bea.com]
Sent: Thursday, December 15, 2005 11:19 AM
To: ws-rx@lists.oasis-open.org
Subject: [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:

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.

ws-rx message