Issue 4397: Another interoperability clarification (ots-structs-ftf) Source: International Business Machines (Dr. Ian Robinson, ian_robinson(at)uk.ibm.com) Nature: Clarification Severity: Summary: Should an Activity service implementation be required to marshal a service context when it sends a reply? To put it another way, should a client Activity service interceptor expect to receive context on a reply if it sent one on a request? I would expect that absence of a context on a reply is fine but this needs to be stated in the specification to ensure interoperability between different vendors' implementations. Resolution: see above Revised Text: For a remote request that completes without exception, the absence of an Activity service context on a response should be taken to mean that the context has not been changed by the target domain. This should be true even in the case where a transaction context is present on both request and response. Actions taken: July 5, 2001: received issue May 2, 2003: closed issue Discussion: Resolution: An implementation should not be required to marshal the context on replies. However, the text needs updating. End of Annotations:===== Importance: Normal Subject: Another interoperability clarification To: ots-structs-ftf@omg.org Cc: issues@omg.org X-Mailer: Lotus Notes Release 5.0.5 September 22, 2000 Message-ID: From: "Ian Robinson" Date: Thu, 5 Jul 2001 11:13:48 +0100 X-MIMETrack: Serialize by Router on d06ml007/06/M/IBM(Release 5.0.6 |December 14, 2000) at 05/07/2001 11:28:30 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-UIDL: -4""!='Ke948n!! From: "Ian Robinson" Date: Thu, 19 Jul 2001 23:03:42 +0100 X-MIMETrack: Serialize by Router on d06ml007/06/M/IBM(Release 5.0.6 |December 14, 2000) at 20/07/2001 08:24:59 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-UIDL: ~7$"!7g!!!$*2!!Pc&e9 Proposal for resolution of 4397: For a remote request that completes without exception, the absence of an Activity service context on a response should be taken to mean that the context has not been changed by the target domain. This should be true even in the case where a transaction context is present on both request and response. Ian Robinson, Senior Software Engineer, WebSphere Development IBM UK Laboratories, Hursley MP 189 Tel (Ext) +44-1962-818626 (Int) 7-248626 ian_robinson@uk.ibm.com From: "Mark Little" To: "XOTS" Subject: FTF meeting summary Date: Wed, 18 Jul 2001 10:05:44 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Filter-Version: 2.1 (cheviot3) Content-Type: text/plain; charset="iso-8859-1" X-UIDL: *%D!!CL[d9H0jd9D]:!! Just a quick note to report on the meeting we had at Danvers. We managed to work through all of the issues that were reported prior to Danvers, though some have come up since. A brief summary of the issues we discussed, and the resolutions follows (the individuals who will write up the final proposed resolutions are also indicated). Proposal for 4397: the absence of a context on a reply means that nothing has changed. Need an extra attribute to the property group. [Ian Robinson to write up.]