OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-rx message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [ws-rx] RE: Issue 115 - mU attribute


I think wsrm:mustUnderstand is too confusing.

Let's suppose I define a new header
        <tns:AllNumbersAreInOctal/>

If I add soap:mU attribute, as I understand the SOAP processing model, 
it's still possible for the application to see "10" and not know it should 
be 8 -- soap mU just say the soap layer has to recognize it, and imposes 
no requirement on the application layer.

Now, if instead I add wsrm:mU, then the RM code must know that 10 really 
means 8, and if it doesn't agree to do that, the recipient has to fault.

Do I have that right?  If so, this is perhaps subtly, but nonetheless 
fundamentally different.  You are really proposing wsrm:DoOrDie, right?

Hope this clarifies the discussion.  As for myself, looking at it that 
way, I'd say that if you want to change the semantics of WSRM then you 
should be in an alternate universe, er namespace, and that DoOrDie seems 
too "icky"

        /r$

--
SOA Appliances
Application Integration Middleware



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]