Issue 2628:  DII, callbacks, and exception holders (messaging-rtf)
Source:  (, )
Nature:  Uncategorized Issue
Severity: 
Summary: Summary: Callback-style invocations use an exception holder valuetype to report
 exceptions to the callback.  The name (and presumably the RepositoryID) of this
 exception holder valuetype is generated by the IDL compiler, and derived from
 the name of the target interface.
 
 When sending a callback-style invocation over the DII, there is no way for the
 ORB to determine the RepositoryID since the name of the target interface is not
 available (in fact, the RepositoryID of the target interface is not available). 
 This makes it impossible for the ORB to report exceptions, as the repository ID
 must be sent with the exception holder in the callback to allow the ORB to
 create the appropriate valuetype.  
 

Resolution: Close no change if the resolution for 2929 is recommended for adoption
Revised Text: 
Actions taken:
May 4, 1999: received issue
May 13, 2002: closed issue
Discussion: 

End of Annotations:=====
Date: Tue, 04 May 1999 16:07:23 -0400
From: "Matthew A. Mihic" <mmihic@iona.com>
Organization: IONA Technologies, Inc.
X-Accept-Language: en
To: messaging-rtf@omg.org, issues@omg.org
Subject: DII, callbacks, and exception holders

Refers orbos/98-05-06.

Callback-style invocations use an exception holder valuetype to report
exceptions to the callback.  The name (and presumably the
RepositoryID) of this
exception holder valuetype is generated by the IDL compiler, and
derived from
the name of the target interface.

When sending a callback-style invocation over the DII, there is no way
for the
ORB to determine the RepositoryID since the name of the target
interface is not
available (in fact, the RepositoryID of the target interface is not
available). 
This makes it impossible for the ORB to report exceptions, as the
repository ID
must be sent with the exception holder in the callback to allow the
ORB to
create the appropriate valuetype.  

I'd suggest allowing the user to specify this id, either via an
attribute on
CORBA::Request, or an additional parameter to CORBA::Request::sendc.
We would
probably also need to add something to the Interface Repository to
allow the
user to correlate an interface with the exception holder for that
interface
(since the name of the exception holder is dependent not only on the
interface
name, but also on the other identifiers defined within the same
scope).

Regards,
Matt

--
Matthew Mihic
IONA Technologies, Inc.
Phone: +1-617-949-4302



Date: Tue, 18 Dec 2001 15:20:34 -0500
From: Jishnu Mukerji <jishnu_mukerji@hp.com>
Organization: Hewlett-Packard Company
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: orb_revision@omg.org
Subject: Proposed resolution for 2628
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-UIDL: Y^V!!/>7!!$M+!!B<-e9

The following resolution for this issue will appear on the next vote
unless there is significant technical objection.

Jishnu.

________________________________________________________________________________

Issue 2812: Callbacks cannot be implemented using DSI (messaging-rtf)

Source: 
Nature:
Severity:
Summary: 

See http://cgi.omg.org/issues/issue2628 for summary and archive.

Resolution: This issue is resolved by the proposed resolution for 2929
Revised Text:
Actions taken: Close this issue if the resolution for 2929 is
recommended for adoption.