Legacy Issue Number: 8586
Source: Zuehlke Engineering ( Frank Pilhofer)
In the CORBA specification, chapter 5 (Value Type
Semantics), section 5.5 (Custom Marshalling), defines
sequences of primitive types in the CORBA module,
i.e., CORBA::StringSeq et al. Some of these types are
then used by the DynamicAny and Portable Interceptor
The presence of these typedefs in section 5.5 seems
to imply that they only need to be defined if the ORB
implements custom marshalling – a feature still
lacking in some open-source and commercial ORBs.
In my experience, having worked with multiple ORBs,
many of them do not provide the complete set of
typedefs in their "orb.idl" file. Many ORBs only
provide a limited set, usually, the set that is
exercised by the other ORB features (such as PI).
This implies that most ORBs added these typedefs
on an "as needed" basis instead of simply referring
to section 5.5.
I suggest to move these typedefs from section 5.5
into chapter 4 (ORB interface), e.g., into section
4.2 (ORB operations) to highlight that these types
should be present even if custom marshalling is not
implemented by the ORB.
In section 5.5.2 (Marshalling Streams), cut the
type definitions, starting with AnySeq, up to and
In section 4.2, in the IDL code fragment, at the
beginning of the CORBA module, paste the type
definitions cut above.
Reported: CORBA 3.0.3 — Thu, 17 Mar 2005 05:00 GMT
Disposition: Deferred — CORBA 3.4
This proposal was generated automatically by request of the Task Force Chair Adam Mitz.
Updated: Mon, 30 Mar 2020 19:47 GMT