ws-rx message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Issue i013 - proposed text changes
- From: Doug Davis <dug@us.ibm.com>
- To: ws-rx@lists.oasis-open.org
- Date: Fri, 5 Aug 2005 18:06:56 -0400
Per my AI on the last conference call
here are the list of changes I propose for the resolution of issue i013:
In the WS-RM Policy doc:
After line 173, add to the normative
outline:
<wsrm:MaxMessageNumber
Number="xs:unsignedLong" ... /> ?
After line 202, add to the more verbose
section of the normative outline:
/wsrm:RMAssertion/wsrm:MaxMessageNumber
A
parameter that specifies the maximum message number that the RM Destination
will accept. If omitted, the default value of the maximum unsigned
long will be assumed.
/wsrm:RMAssertion/wsrm:AcknowledgementInterval/@Number
The
maximum message number.
After line 434, add to the schema:
<xs:element
name="MaxMessageNumber" minOccurs="0" >
<xs:complexType>
<xs:attribute name="Number"
type="xs:unsignedLong"
use="required" />
<xs:anyAttribute namespace="##any" processContents="lax"
/>
</xs:complexType>
</xs:element>
thanks
-Doug
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]