Issue 8586: Moving *Seq typedefs into ORB chapter (corba-rtf)
Source: Zuehlke Engineering (Mr. Frank Pilhofer, fpilhofer2008(at)gmail.com)
Nature: Uncategorized Issue
Severity: 
Summary: 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
chapters.


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.


Proposed resolution:


In section 5.5.2 (Marshalling Streams), cut the
type definitions, starting with AnySeq, up to and
including WStringSeq.


In section 4.2, in the IDL code fragment, at the
beginning of the CORBA module, paste the type
definitions cut above.
Resolution: 
Revised Text: 
Actions taken:
March 17, 2005: received issue
April 11, 2012: Deferred
Discussion: 

End of Annotations:=====
ubject: Moving *Seq typedefs into ORB chapter 
Date: Thu, 17 Mar 2005 10:54:00 -0500 
Thread-Topic: Moving *Seq typedefs into ORB chapter 
Thread-Index: AcUrCYjPMeBgPVOsQQGCwD9RSe926A== 
From: "Pilhofer, Frank" <fpilhofe@mc.com> 
To: <corba-rtf@omg.org> 
X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id j2HG8214010470 


This is a new issue for the CORBA RTF.


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
chapters.


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.


Proposed resolution:


In section 5.5.2 (Marshalling Streams), cut the
type definitions, starting with AnySeq, up to and
including WStringSeq.


In section 4.2, in the IDL code fragment, at the
beginning of the CORBA module, paste the type
definitions cut above.