Previous | Table of Contents | Next |
Name spaces within the CORBA interface repository are conceptually similar to COM type libraries. However, the CORBA interface
repository looks, to the client, to be one unified service. Type libraries, on the other hand, are each stored in a separate
file. Clients do not have a unified, hierarchical interface to type libraries.
Table 18-6 defines the mapping between equivalent CORBA and COM interface
description concepts. Where there is no equivalent, the field is left blank.
Table 18-6 CORBA Interface Repository to OLE Type Library Mappings
TypeCode | TYPEDESC | ||||
Repository | |||||
ModuleDef | ITypeLib | ||||
InterfaceDef | ITypeInfo | ||||
AttributeDef | VARDESC | ||||
OperationDef | FUNCDESC | ||||
ParameterDef | ELEMDESC | ||||
TypeDef | ITypeInfo | ||||
ConstantDef | VARDESC | ||||
ExceptionDef |
Using this mapping, implementations must provide the ability to call Object::get_interface on CORBA object references to COM
objects to retrieve an InterfaceDef. When CORBA objects are accessed from COM, implementations may provide the ability to
retrieve the ITypeInfo for a CORBA object interface using the IProvideClassInfo COM interface.