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] issue 115: clarifying question

Why would anything need to go in the header? The spec that defines the header would define what if any relationship it had to body content.


Marc Goodner

Technical Diplomat

Microsoft Corporation

Tel: (425) 703-1903

Blog: http://spaces.msn.com/mrgoodner/

From: Gilbert Pilz [mailto:Gilbert.Pilz@bea.com]
Sent: Monday, April 24, 2006 2:41 PM
To: wsrx
Subject: [ws-rx] issue 115: clarifying question


During the conference call of 4/20/2006 Chris asserted that you can use a SOAP header with a mustUnderstand attribute to flag the fact that some element in either another header or in the message body is an extension that must be understood by the receiver. I'm not sure I understood exactly what Chris thought this should look like. For example, imagine the following CreateSequence message. The extension elements have been marked in bold. What is supposed to go in the <wsrm:Extension> header?

<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="
  <wsrm:Extension S:mustUnderstand="1">

I'm sure that most of us could all come up with a reasonable design to do what you suggest, but for the purposes of further discussion I'd like to know what design Chris had in mind?

- gp

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