Summary:
Summary: (D)IForeignComplexType,(D)ICORBAStruct,(D)ICORBAUnion,(D)IForeignException,(D)ICORBAUserException should have standard UUIDs and UUID identifiers
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: Section 4.1.12: DICORBAtypeCode::kind has one parameter of type TCKind. It should be of type CORBATCKind
Summary: There should be a standard ProgramId for the class which exposes D(I)CORBAAny
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: 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: I suggest that the automation chapter be changed to align with the architecture chapter
Summary: The uuid for DForeignException has an extra 0. It should be E977F907-3B75-11cf-BBFC-444553540000
Summary: This property should be removed because the INSTANCE_repositoryId property in IForeignComplexType provides this functionality
Summary: When translating a BSTR to a CORBA bounded string, boundary violations should cause the View to propagate DISP_E_OVERFLOW
Summary: Second to last paragraph of the section contains the term "CORBA proxy" which should be changed to Automation View Interface.
Summary: The "retval" attribute should be removed from the second argument in both methods. MIDL does not have a retval attribute
Summary: INSTANCE_Clone does not need an in-parameter to specify the instance to be cloned.
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: 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: There should be straight dispatch versions of DCORBAObject and DORBObject
Summary: In lock duration of Section 7.1 there are two descriptions. The role of the clients is vague to me
Summary: In the specification, "Related lock sets" appears only in "create_related()" and create_transaction_related()" Where do I use these methods
Summary: There is inconsistency regarding which model ConcurrencyControl needs to support
Summary: I understand the params to be name value pairs of columns and the values for the
selection, update, delete, insert criteria
what is in the query? I would think if this is the whole query why would you
need the params??
Summary: When multiple union labels resolve to the same union member, the property accessor for that union member has an additional (optional) argument
Summary: Change the layout of both bounded and unbounded sequences to be the same
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: 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: Example of "on both machines" does nor correspond to the diagrams. Add "on an intermediate machine" to sentence
Summary: There are a bunch of code samples that use a different font than the rest of the document
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: On page 9, paragraph beginning with "Within an interface...." should read "..attributes should appear after operations..."