Re: [wsrm] New merged schema for messageHeader and request elements

[Tom Rutt <tom@coastin.com>]

Sunil Kunisetty wrote:

> While I'm not against this, I'd like to bring up the rationale for having this
> abstraction in the first place.
> i) Because MessageHeader is used by all other RM Headers. Ofcourse
>    this is no a longer an issue as we identified that it is only needed for
>    Request.
> ii) If in the future, a standard "Message Header" mechanism gets standardized
>     so that it could be used across other services (say Security etc...), we can
>     easily adopt to it by swapping our MessageHeader with that.
>
>  I far one don't believe that (ii) is a big issue, but just reminding others.
>
It would have to have our concept of reply pattern, as well as our 
message id group id and group termination parameters.

This stuff is pretty particular to ws reliablity.

TomRUtt

>
> -Sunil
>
>Tom Rutt wrote:
>
>  
>
>>The following is a merged schema for the message header merged into the
>>request element.
>>
>>-----
>><!-- The request header Type and it's elements-->
>>    <xsd:complexType name="RequestType">
>>        <xsd:complexContent>
>>            <xsd:extension base="wsrm:RmBaseType">
>>                <xsd:sequence>
>>                    <xsd:element name="MessageId"
>>type="wsrm:MessageIdType"/>
>>                    <xsd:element name="ExpiryTime" type="xsd:dateTime"/>
>>                    <xsd:element name="ReplyPattern"
>>type="wsrm:ReplyPatternType"/>
>>                    <xsd:element name="AckRequested"
>>type="wsrm:EmptyType" minOccurs="0"/>
>>                    <xsd:element name="DuplicateElimination"
>>type="wsrm:EmptyType" minOccurs="0"/>
>>                    <xsd:element name="MessageOrder"
>>type="wsrm:EmptyType" minOccurs="0"/>
>>                </xsd:sequence>
>>            </xsd:extension>
>>        </xsd:complexContent>
>>    </xsd:complexType>
>> -
>>
>>Here is a an example
>>
>><?xml version="1.0" encoding="UTF-8"?>
>><!--Sample XML file generated by XMLSPY v5 rel. 4 U
>>(http://www.xmlspy.com)-->
>><Request
>>xmlns="http://www.oasis-open.org/committees/wsrm/schema/1.1/SOAP1.1";
>>soap:mustUnderstand="1">
>>    <MessageId groupId="http://www.altova.com/1";>
>>        <SequenceNum number="4294967295" status="Start"
>>groupExpiryTime="2001-12-17T09:30:47-05:00" />
>>    </MessageId>
>>    <ExpiryTime>2001-12-17T09:30:47-05:00</ExpiryTime>
>>    <ReplyPattern replyTo="http://www.altova.com";>Callback</ReplyPattern>
>>    <AckRequested/>
>>    <DuplicateElimination/>
>>    <MessageOrder/>
>></Request>
>>
>>This simplifies the protocol description a lot.  This element would only
>>be present for rm requests with a payload.
>>
>>Tom Rutt
>>
>>--
>>----------------------------------------------------
>>Tom Rutt                email: tom@coastin.com; trutt@fsw.fujitsu.com
>>Tel: +1 732 801 5744          Fax: +1 732 774 5133
>>
>>To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsrm/members/leave_workgroup.php.
>>    
>>
>
>
>To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsrm/members/leave_workgroup.php.
>
>  
>


-- 
----------------------------------------------------
Tom Rutt		email: tom@coastin.com; trutt@fsw.fujitsu.com
Tel: +1 732 801 5744          Fax: +1 732 774 5133