RE: [ws-caf] [Bug 130] New: SOAP mustUnderstand should not be determined by ws-context

["Furniss, Peter" <Peter.Furniss@choreology.com>]

Sorry, I must have clicked the commit button twice. 130 should be closed
immediately as duplicate of 129,

Peter

> -----Original Message-----
> From: bugzilla-daemon@arjuna.com [mailto:bugzilla-daemon@arjuna.com] 
> Sent: 26 May 2004 12:31
> To: ws-caf@lists.oasis-open.org
> Subject: [ws-caf] [Bug 130] New: SOAP mustUnderstand should 
> not be determined by ws-context
> 
> 
> http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=130
> 
>            Summary: SOAP mustUnderstand should not be 
> determined by ws-
>                     context
>            Product: WS-Context
>            Version: 1.0
>           Platform: PC
>         OS/Version: Windows 2000
>             Status: NEW
>           Severity: normal
>           Priority: P2
>          Component: Implementation and interoperability
>         AssignedTo: ws-caf@lists.oasis-open.org
>         ReportedBy: peter.furniss@choreology.com
>          QAContact: mark.little@arjuna.com
> 
> 
> Draft 0.2, section 2.1 says that SOAP:mustUnderstand must be 
> true for a context 
> sent with an application message.  WS-Context should not 
> specify this - it 
> should be left to a higher level. There will certainly be 
> some cases where a 
> context is propagated in hope, but not certainty, that it 
> will be recognised. A 
> referencing specification could mandate a value, or leave it 
> to the particular 
> use.
> 
> It should be stated that SOAP:mustUnderstand=1 on a 
> ws-context means the 
> receiver is required to understand the particular 
> context-type, not just that 
> it is a ws-context.
> 
> 
> 
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>