Issues for COMCORBA Revision Task Force mailing list

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 16: Ordering of user exception and return values
Issue 679: Incorrect mappings for systems exceptions (part A)
Issue 680: Standard uuid for interfaces (COM/CORBA Part A)
Issue 681: Section 4.1.18.5 enum should be named CORBA_CompletionStatus
Issue 682: VB cannot handle array out-parameters
Issue 683: What should Automation View accept in bounded sequences?
Issue 684: Standard ProgramId
Issue 685: Section 4.1.12: DICORBA TypeCode::kind
Issue 686: Remove EX_repositoryID readonly property from IForeignException
Issue 687: Add CORBATCKind to end of enum list
Issue 688: Return value type of DICORBATypeCode::member_type should be changed
Issue 689: uuid for DForeignException has an extra 0
Issue 690: page 2-25 contradicts first sentence of 3rd full para on p 4-106
Issue 691: ODL is erroneous
Issue 692: Page 2-41, section 2.9.7.2 Add name for Automation View interface
Issue 693: page 2-30: There is a label "Examples", but no examples
Issue 694: page 4-109, section 4.1.5.3: editorial
Issue 695: boundary violations should cause View to propagate DISP_E_OVERFLOW
Issue 696: page 4-129, section 4.1.17.1: retval attribute
Issue 697: page 4-129, section 4.1.17: change term "CORBA proxy"
Issue 698: INSTANCE_Clone does not need an in-parameter
Issue 699: Dispatch versions of DCORBAObject and DORBObject
Issue 700: Automation View should generate HRESULT DISP_E_TYPEMISMATCH
Issue 701: Changes to ForeignComplexType
Issue 702: Levels of Indirection for passing COM types
Issue 703: COM Sequence changes
Issue 704: Duplicate union labels
Issue 707: Section 13A.2.3: editorial
Issue 708: Section 13A.5.2: Editorial
Issue 709: Capter 13C: Editorial
Issue 710: Section 13C.1.3 Editorial

Issue 16: Ordering of user exception and return values (comcorba-rtf)

Summary: The COM/CORBA Part A spec states that user exceptions go after return values in one place, and before return values in another. (3.2.10.3 and 4.1.3.1)

Summary: Section 4.1.18.6 Table 4-14: A few of these mappings don"t seem to make sense (i.e. the meaning of the different exceptions in each object system is much different

Summary: (D)IForeignComplexType,(D)ICORBAStruct,(D)ICORBAUnion,(D)IForeignException,(D)ICORBAUserException should have standard UUIDs and UUID identifiers

Summary: The enum should be named CORBA_CompletionStatus instead of CORBA_ExceptionType

Summary: The VB cannt handle array out-parameters. Must use in-outs.

Summary: When mapping bounded sequences, should the Automation View accept as an in-parameter a Safearray whose upper bound is less than the maximum lenght of the mapped sequence?

Summary: There should be a standard ProgramId for the class which exposes D(I)CORBAAny

Summary: Section 4.1.12: DICORBAtypeCode::kind has one parameter of type TCKind. It should be of type CORBATCKind

Summary: This property should be removed because the INSTANCE_repositoryId property in IForeignComplexType provides this functionality

Summary: Enum CORBATCKind omits the boolean kind (p.4-123, section 4.1.12) I recommend adding it to the end of list to preserve backward compatibility. Also missing tk_char.

Summary: The return value type should be DICORBATypeCode*, not IDispatch. The return value of member_label should be a DICORBAAny* rather than VARIANT

Summary: The uuid for DForeignException has an extra 0. It should be E977F907-3B75-11cf-BBFC-444553540000

Summary: I suggest that the automation chapter be changed to align with the architecture chapter

Summary: ODL which shows an extra, optional parameter for exception information on property-get or property-set method is erroneous, since MKTYPLIB doesn"t allow extra parameter on property accessor

Summary: There should be a standard name for the Automation View interface.

Summary: Page 2-30, top of page, end of section 2.7.1: There is a label "Examples:" but no example follows

Summary: "..maximum value of an Automation short" should read "..maximum value of a CORBA::UShort

Summary: When translating a BSTR to a CORBA bounded string, boundary violations should cause the View to propagate DISP_E_OVERFLOW

Summary: The "retval" attribute should be removed from the second argument in both methods. MIDL does not have a retval attribute

Summary: Second to last paragraph of the section contains the term "CORBA proxy" which should be changed to Automation View Interface.

Summary: INSTANCE_Clone does not need an in-parameter to specify the instance to be cloned.

Summary: There should be straight dispatch versions of DCORBAObject and DORBObject

Summary: If number of dimensions of an input SAFEARRAY does not match the mapped CORBA type, the Automation View should generate the HRESULT DISP_E_TYPEMISMATCH

Summary: The following methods should be added to DIForeignComplexType, IID should be changed: string type_name(); string scoped_name(); string_repository_id(); more details in corresponding archive file

Summary: 

Summary: Change the layout of both bounded and unbounded sequences to be the same

Summary: When multiple union labels resolve to the same union member, the property accessor for that union member has an additional (optional) argument

Summary: Example of "on both machines" does nor correspond to the diagrams. Add "on an intermediate machine" to sentence

Summary: Third bullet should read:"...are sorted based upon interface name.."  Last bullet should read "..the operations introduced in the current interface are mapped last and ordered.."

Summary: There are a bunch of code samples that use a different font than the rest of the document

Summary: On page 9, paragraph beginning with "Within an interface...." should read "..attributes should appear after operations..."