Unexpected element exception from file geneated from playlist

[dalcorta]

I generated a orchestra file using the playlist app, and it contains a namespace that causes the generator to crash.

Exception in thread "main" java.lang.RuntimeException: XML Validation Exception: unexpected element (uri:"http://fixprotocol.io/2022/orchestra/appinfo/fixml", local:"FIXMLencodingType"). Expected elements are <{}text> at row: 19353 column: 51

The namespace is used in these structures for example:

<fixr:field id="8" abbrName="BeginString" updated="FIX.Latest" type="BeginStringCodeSet" name="BeginString" updatedEP="270" added="FIX.2.7"> <fixr:annotation> <fixr:documentation purpose="SYNOPSIS"> Identifies beginning of new message and session protocol version by means of a session profile identifier (see FIX Session Layer for details). ALWAYS FIRST FIELD IN MESSAGE. (Always unencrypted).</fixr:documentation> <fixr:appinfo purpose="FIXML"> <fixml:FIXMLencodingType notReqXML="1"/> </fixr:appinfo> </fixr:annotation> </fixr:field>

<fixr:componentRef updatedEP="192" id="1021" updated="FIX.5.0SP2" added="FIX.4.4"> <fixr:annotation> <fixr:appinfo purpose="FIXML"> <fixml:FIXMLencodingType inlined="1"/> </fixr:appinfo> <fixr:documentation> Required if NoUnderlyings(711) &gt; 0.</fixr:documentation> </fixr:annotation> </fixr:componentRef>

[kleihan]

@dalcorta the code to convert Orchestra to protobuf was written before FIX decided to use the appinfo element in Orchestra to add information required to create FIXML schema from Orchestra. The main information is whether an element is required for FIXML or not, e.g. repeating group counters (NoXXX fields) are never required for FIXML.

The Orchestra V1.0 standard defines appinfo with <xs:any processContents="lax"/>. The elements inside appinfo should hence be ignored and not validated.

You will not need these FIXML elements inside appinfo for protobuf. As a workaround, you can remove appinfo elements with purpose="FIXML" prior to converting the Orchestra file.