[orchestra2unified] Missing component type for (Derivative/Leg/Underlying)SecurityXML

[kleihan]

Unified requires the type of a component to be specified:

	<xs:element name="component">
		<xs:complexType>
			<xs:sequence>
				<xs:element ref="messageEntity" minOccurs="0" maxOccurs="unbounded"/>
			</xs:sequence>
			<xs:attributeGroup ref="entityAttribGrp"/>
			<xs:attribute name="id" type="id_t" use="required"/>
			<xs:attribute name="name" type="xs:string" use="required"/>
			<xs:attribute name="type" type="ComponentType_t" use="required"/>
			<xs:attribute name="repeating" type="BOOL_t" use="optional"/>
			<xs:attribute name="category" type="xs:string" use="optional"/>
			<xs:attribute name="abbrName" type="xs:string" use="optional"/>
			<xs:attribute name="notReqXML" type="BOOL_t" use="optional"/>
			<!-- would like to force a description of the component -->
		</xs:complexType>
	</xs:element>

FIX has four components with the type "XMLDataBlock", (Derivative/Leg/Underlying)SecurityXML. This type is not generated for them, e.g.

        <fixr:component name="SecurityXML" id="1060" category="Common" 
                   added="FIX.5.0" updated="FIX.5.0SP2" updatedEP="145" abbrName="SecXML">

We have more than one option to solve this:

1. Exception list (=hard-coded)
2. Adding another appinfo element, created by unified2orchestra
3. ...

[donmendelson]

@kleihan would you agree that it's unlikely we'll ever add another XMLDataBlock? Since there are only 4 instances, I'm inclined to hard-code it the transposer. Requiring markup in the Orchestra file seems more error-prone.

[kleihan]

@donmendelson I would agree, we do not have component types in Orchestra as a concept. It is a legacy issue affecting 4 components as long as we have to generate Unified for backward compatibilty.