Issue 751: Inclusion of standard exception (orb_revision) Source: (, ) Nature: Uncategorized Issue Severity: Significant Summary: Summary: The proposal is to define a new standard exception, called EXTERNAL_ACCESS (the name is not important) that carries an any value. Another alternative may be to re-define the exception COMM_FAILURE so that it may carry an any in addition to the existing minor and completed fields. Resolution: close no change in 2.4 Revised Text: Actions taken: October 6, 1997: received issue August 12, 1999: closed issue Discussion: Not clear that an RTF is the right place for adding such featurelets. This should be added as part of some appropriate submission to some RFP. End of Annotations:===== Return-Path: Date: Mon, 6 Oct 1997 11:44:06 -0600 From: Juan Hierro Subject: Yet another three issues (the lasts, I promise !) To: juergen@omg.org Cc: jhierro@ovdm36.cnd.hp.com Content-Md5: k1zAVq2huoVvGDsUtg6OHQ== ORB Issues: =========== Title: Inclusion of a standard exception that operations on attributes may raise to carry additional info. Description: One of the most important benefits of using CORBA is its value as a technology to integrate heterogeneous systems that are not necessarely based on CORBA. In that context, CORBA can be used to encapsulate access to non-CORBA systems and bridge can be developed that enable to present a CORBA 'view' of a existing non-CORBA system. Developing such bridges typically involve mapping the interface a non-CORBA system provides into OMG IDL. Some operations that are visible through the interface of an external system may be better mapped as attributes associated to an interface defined in OMG IDL. Bridges would convert requests associated to attributes into requests of a specific protocol that gives access to the external system (a remote Database, a CMIP or SNMP agent, etc). There may be protocol errors that are detected in the bridge that would be properly mapped as exceptions. In the case of attributes, the only alternative is to raise a standard exception. However, those standard exception cannot carry any specific info that helps. The proposal is to define a new standard exception, called EXTERNAL_ACCESS (the name is not important) that carries an any value. Another alternative may be to re-define the exception COMM_FAILURE so that it may carry an any in addition to the existing minor and completed fields.