[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [Bug 134] New: mustUnderstand needs moving and defining
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=134 Summary: mustUnderstand needs moving and defining Product: WS-Context Version: 1.0 Platform: PC OS/Version: Windows 2000 Status: NEW Severity: normal Priority: P2 Component: Text and diagrams AssignedTo: ws-caf@lists.oasis-open.org ReportedBy: peter.furniss@choreology.com QAContact: mark.little@arjuna.com the mustUnderstand and mustPropagate attributes should be moved to context and don't belong on the service list. Since a context is (commonly) a soap header, the SOAP:mustUnderstand attribute is available, and mustUnderstand could be considered superfluous. However, the SOAP:mustUnderstand attribute could be interpreted as meaning the ws-context-specified aspects must be understood, and the wsctx:mustUnderstand means the context type must be understood. Thus SOAP:mustUnderstand="1" wsctx:mustUnderstand="0" wsctx:mustPropagate="1" would mean the receiver was guaranteed to propagate the context unchanged if it did not recognise the context type (or through a soap fault). (if it did recognise the context type, it could sort out the propagation for itself) This latter approach seems to add necessary functionality to support the two- level function identification of ws-context (context namespace of whole header; context type as particular protocol). It may be better to rename wsctx:mustUnderstand to avoid (human) confusion with the SOAP attribute. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]