-
Key: CORBA26-56
-
Legacy Issue Number: 4073
-
Status: closed
-
Source: Anonymous
-
Summary:
See the CORBA Components specification, orbos/99-07-01, chapters 5, 6,
7, and 9. The semantics, life cycle, and mechanisms behind components,
facets, "regular" objects, and their related object references is weakly
specified. In particular, it is not clear how a component interacts
with a container to generate an object reference to a facet, especially
a facet in a secondary segment. The description of component
identifiers indicates that the component object id, the facet number,
and the segment number are used to generate the facet's object reference
(or perhaps only the ObjectId), but the sequence of operations is not
given. It appears that not all the necessary methods have been formally
specified, nor are the code generation examples adequate for this
siutation.Consider the following IDL:
interface A {};
{ provides A a_facet; A get_another_A(); }
component C
;
What is the life-cycle of the A object returned as the provided facet?
Is it limited to the life-cycle of the component? Is the member
operation returning an object of the same type as a provided facet
permitted? Should this return the same object as the facet? If not, is
the life-cycle of this extra object limited to the life-cycle of the
component? Should such objects be considered facets, even if not
explicitly declared such (which, please note, provides the equivalent of
the deprecated "provides multiple" capability)? What information needs
to be encoded in its object reference, especially for component
dependency? How will the context for this be established, and are any
additional interfaces or operations required to accomplish this? -
Reported: CORBA 2.4.1 — Tue, 21 Nov 2000 05:00 GMT
-
Disposition: Resolved — CORBA 2.6.1
-
Disposition Summary:
rejected
-
Updated: Fri, 6 Mar 2015 20:58 GMT
CORBA26 — Components, Facets, and Object References Unclear
- Key: CORBA26-56
- OMG Task Force: Core RTF