Issue 680:  Standard uuid for interfaces (COM/CORBA Part A) (comcorba-rtf)
Source:  (, )
Nature:  Uncategorized
Severity: 
Summary: Summary: (D)IForeignComplexType,(D)ICORBAStruct,(D)ICORBAUnion,(D)IForeignException,(D)ICORBAUserException should have standard UUIDs and UUID identifiers

Resolution: 
Revised Text: 
Actions taken:
August 25, 1997: received issue
Discussion: 

End of Annotations:=====
COM-CORBA Part A Errata and Issues for Revision Task Force
David Frankel, Genesis Development Corporation

Notes: * indicates that this point was submitted to Valerie Hurley for
the OMG edit.   Section numbers are from the spec as submitted by the
submitters dated 31 January, 1996.  Dates simply represent the date
when the matter was noted.

7 2/15/96-There should be a standard uuid for the following
interfaces. These are all interfaces which are simply base classes and
which thus are never used except in derived form.   It is helpful when
handed a DICORBAAny pointer that wraps a dispatch pointer-you can QI
on the pointer to determine what you've been handed.  Both the dual
(DI) and straight dispatch (D) versions of the interfaces should have
standard UUIDs and UUID identifiers:
7 (D)IForeignComplexType
7 (D)ICORBAStruct
7 (D)ICORBAUnion
7 (D)IForeignException 
7 (D)ICORBAUserException
 Implementations of the dual (DI..) form of the interface should
answer affirmatively to a QueryInterface for the straight dispatch (D)
form of the interface. This would be valid, since a dual derives from
IDispatch.  Thus, software which is not dual-aware can still
interoperate with the dual-aware implementation.