[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [Bug 221] New: Parameters and Context on BEGIN and BEGUN?
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=221 Summary: Parameters and Context on BEGIN and BEGUN? Product: WS-Context Version: 1.0 Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Text and diagrams AssignedTo: ws-caf@lists.oasis-open.org ReportedBy: tony.fletcher@choreology.com QAContact: mark.little@arjuna.com WS-Context Section 5.2 ‘Context Service messages’ Begin subheading states: 'The begin operation creates a new context (based on the type parameter). If a context is present on the begin message then the new context is automatically nested with that context in a parent-child relationship, i.e., the propagated context is the immediate parent in the parent-contexts element, which MUST be set in the returned context.' However, the following text does not describe or even mention neither a type parameter nor a context parameter. The Begun message seems to have no standard parameters. The schema for Begin has neither a type nor a context parameter and for Begun it does not have a context parameter. If the idea is that the context is carried as a Header while the message is carried in the Body this should be described in text, where this is the case, and added to the WSDL, which currently does not help. Note that a context parameter is included in the ‘contents’ and ‘set-contents’ message definitions in the schema. ------- 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]