Issue 2537: TIMEOUT system exception not mentioned in section 5.3.4 (messaging-rtf) Source: (, ) Nature: Uncategorized Issue Severity: Summary: Summary: 2) The TIMEOUT system exception is defined in 5.2.2.3. It is actually used in the policies defined in sections under 5.3.4, but never mentioned there. It should be mentioned in those sections where it applies, and its actions clarified but see the following related issue. Resolution: close issue Revised Text: Actions taken: March 15, 1999: received issue October 3, 2001: closed issue Discussion: this issue has been resolved. The text no longer refers to a Messaging:TIMEOUT exception. It does use CORBA:TIMEOUT, but does not (re)define it. It is defined in 4.11.3.33 of the 2.4 Spec. Close the issue. End of Annotations:===== X-Sender: siegel@192.67.184.65 Date: Sat, 13 Mar 1999 12:58:57 -0500 To: issues From: Jon Siegel Subject: three issues on AMI Hi -- Here are three issues on AMI: 2) The TIMEOUT system exception is defined in 5.2.2.3. It is actually used in the policies defined in sections under 5.3.4, but never mentioned there. It should be mentioned in those sections where it applies, and its actions clarified but see the following related issue. Sender: Chris.Smith@uab.ericsson.se Message-ID: <383FE0F6.93E3EFB3@uab.ericsson.se> Date: Sat, 27 Nov 1999 14:47:34 +0100 From: Chris Smith Organization: Ericsson Utvecklings AB X-Mailer: Mozilla 4.7C-CCK-MCD [en] (X11; U; SunOS 5.6 sun4u) X-Accept-Language: sv,en-US MIME-Version: 1.0 To: messaging-rtf@omg.org, uabcsru@uab.ericsson.se Subject: Proposed Resolutions of Messaging Editorials Content-Type: multipart/mixed; boundary="------------0A91F7BE2EEB457805FF7789" X-UIDL: G42e9k8c!![Bid9k?)e9 Issue 2352: Errant Messaging::Timeout (messaging-rtf) Summary: The typedef for Messaging::Timeout is never used in the rest of the specification. Proposed Solution. The typedef was errantly left into the specification but is never used. It should be deleted from the IDL in section 5.3 and the summary IDL in 10.3. Issue 2506: wording changes in AMI section 3.3.2 (messaging-rtf) Summary: The following wording changes are needed in Section 3.3.2: In the first sentence, change "to support interoperability and Time Independent Invocations" to "to support interoperability of Time Independent Invocations". and in the second sentence of the first bullet, change "deferred synchronous" to "asynchronous". Proposed Solution - As described in issue. Issue 2537: TIMEOUT system exception not mentioned in section 5.3.4 (messaging-rtf) Summary: 2) The TIMEOUT system exception is defined in 5.2.2.3. It is actually used in the policies defined in sections under 5.3.4, but never mentioned there. It should be mentioned in those sections where it applies, and its actions clarified but see the following related issue. Proposed Solution - Mention in section 5.3.4.6. Exact text will be in resolution to issue 2538. [] Chris.Smith3.vcf Date: Tue, 20 Mar 2001 18:15:02 -0500 From: Jishnu Mukerji Organization: Hewlett-Packard EIAL, Florham Park NJ USA X-Mailer: Mozilla 4.73 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: orb_revision@omg.org Subject: Issue 2537 proposed resolution Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-UIDL: "b/e9jJ~!!7