Issue 3544: Inheritance of ExceptionHolders (formerly issue 2658) (messaging-rtf)
Source: Perot Systems (Mr. Charles W. Binko, nobody)
Nature: Uncategorized Issue
Severity: 
Summary:  In the Messaging Spec, it is not specified whether ExceptionHolders should mirror the inheritance tree of the interfaces that they support.
Resolution: close issue, no change
Revised Text: 
Actions taken:
May 18, 1999: received issue
October 3, 2001: closed issue
Discussion: 
Per the chair of the now deefunct Messaging RTF Chris Smith "This issue 
has already been dealt with but it has come back with a new number due to OMG losing 
some issues." So propose close no change. 

End of Annotations:=====
Date: Mon, 21 May 2001 16:45:13 -0400
From: Jishnu Mukerji <jishnu_mukerji@hp.com>
Reply-To: jishnu_mukerji@hp.com
Organization: Hewlett-Packard EIAL, Florham Park NJ, USA
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: orb_revision@omg.org
Subject: Issue 3543 Proposed Resolution
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-UIDL: &'He9Wh?e9D/~e9A~<!!

The following resolution will appear in the next vote unless any
serious
problems are discovered in it.

Jishnu.
___________________________________________________________________________
Issue 3543: PersistentRequest::get_reply -- read once, or read many
(formerly issue2163
(messaging-rtf)

Nature: Uncategorized Issue 
Severity: 
Summary: Can a client call PersistentRequest::get_reply multiple times
on the same request and receive a valid reply each time? Or should the
first call "clear out" the reply such that subsequent calls raise an
exception? 

Resolution: Section 22.14.2.9 clearly states that: "If a response is
returned to the caller, the PersistentRequest is deactivated so that
future invocations of get_reply raise the system exception
OBJECT_NOT_EXIST." 

This is further reiterated in section 22.14.2.8 where it says: "This
attribute cannot be checked if the response has already been delivered
to some caller of get_reply, as the PersistentRequest object will have
been deactivated at that time and the ORB will return the system
exception OBJECT_NOT_EXIST on any subsequent invocation on that
PersistentRequest." 

Seems like there is no ambiguity on this metter and therefore no
further
clarification is necessary. 

Revised Text: 

Actions taken: Close issue no change. 
--