XMLtoAVRO mapping issue in CAP message

[JoaquinMB-Freq]

During the step1 of the integration of Merlin CrisisSuite into the Testbed for the Trial 2 (DryRun1), Merlin and later Thales, reported that their CAP messages are truncated in the element

<alert>
   <info>
      <resource>

This is, the resource's child nodes were not mapped to AVRO, hence not stored properly in the topic.

This happened when using the test-bed REST adapter and it blocked the integration of SMAP (Thales) and Crisis Suite (Merlin) for Dry Run 1 (Trial 2).
Opening the ticket for further research and unblock the situation.

[JoaquinMB-Freq]

@thoobr has found out the reason. It seems that the problem was from a limitation of the XMLtoAVRO mapper (repository xml-avro, forked from elodina/xml-avro).
The mapper can't work with optional parameters that are not defined in the schema as such.
Additionally, it is worth to mention that the mapping is case sensitive.