Issue 3347: Python Issue: Dynamic Invocation Interface                                                                                                                                                              (python-ftf)
Source: Camros Corporation (Mr. Jeffrey A. Marshall, jam@camros.com)
Nature: Uncategorized Issue
Severity: 
Summary: In the third paragraph of Section 14.4.4 states that "The application may 
specify the repository id of the target object.". 

I assume that this is done in order for the ORB to lookup the operation in 
the given interface in and be determine parameter type/direction and return 
value information.

This raises the following issues:
  - What exception is raised if the repository id is invalid (ie, can't be 
looked up in the IFR, etc...)
  - "Standard" operations (ie, _is_a, _interface, etc...) are not defined in 
the IFR so these need to be handled separately than other operations

Should we also provide a "standard" operation (similar to C++) which takes 
something like a NamedValuePair sequence (or better yet a 
CORBA::OperationDescription)?

Resolution: issue rejected, closed
Revised Text: 
Actions taken:
February 22, 2000: received issue
October 10, 2000: closed issue
Discussion: 
The exception to use when the IFR is not available is specified as INTF_REPOS in the Core. Calling pseudo-operations on the DII is not supported, according the DII specification in the Core.
End of Annotations:=====
Date: Tue, 22 Feb 2000 15:36:22 -0500 (EST)
Message-Id: <200002222036.PAA21866@emerald.omg.org>
To: python-ftf@omg.org, issues@omg.org
Subject: Python Issue: Dynamic Invocation Interface
From: "Jeffrey A. Marshall" <jam@camros.com>
X-Mailer: TWIG 2.1.1
Content-Type: text
X-UIDL: 3>j!!&Xad9:$Z!!VO&!!

In the third paragraph of Section 14.4.4 states that "The application
may 
specify the repository id of the target object.". 

I assume that this is done in order for the ORB to lookup the
operation in 
the given interface in and be determine parameter type/direction and
return 
value information.

This raises the following issues:
  - What exception is raised if the repository id is invalid (ie,
can't be 
looked up in the IFR, etc...)
  - "Standard" operations (ie, _is_a, _interface, etc...) are not
defined in 
the IFR so these need to be handled separately than other operations

Should we also provide a "standard" operation (similar to C++) which
takes 
something like a NamedValuePair sequence (or better yet a 
CORBA::OperationDescription)?

-- 
Jeffrey A. Marshall

Camros Corporation
Email  jam@camros.com
Voice  703-876-1700 ext. 10
Fax    703-876-1818
       http://www.camros.com/