[Bug 221] Parameters and Context on BEGIN and BEGUN?

[bugzilla-daemon@arjuna.com]

http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=221





------- Additional Comments From mark.little@arjuna.com  2005-02-17 11:37 -------
It is stated in 5.2 that context may be present - does not say how, but implies
in header if using SOAP.  This would be spelt out in the binding. 
Add a table that states which messages must have a context with them and which
ones may optionally have a context with them.

Doug pointed out that it was his understanding that there could be several
contexts with BEGIN and the service picks the one that corresponds to the type
in BEGIN and builds a new context for BEGUN with the selected one.  This raises
an issue of should BEGUN echo all the other BEGIN contexts?

There is a related issue as to why 'get' and 'set' have context explicitly
embedded in the message.

Current text does not say a context within a context has to be of same type.  It
was agreed to log a new issue on multiple contexts on one message, and also to
log another new issue as to why 'get' and 'set' have embedded contexts.

State when a context is required and when optional on each operation and clean
up the text on types of contexts. 
Tony motioned and Mark seconded this proposal and it was passed unanimously.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.