XTCE12 — CommandContainer under the MetaCommand

In the CommandContainer under the MetaCommand, inside the EntryList,
there is a division between groupings of the Parameter/ContainerRefEntries
and the FixedValue/ArgumentRefEntries. The problem is what this does is
make you have to define ALL your ParameterRefEntries and ContainerRefEntries
BEFORE defining any FixedValues or ArgumentRefs inside a CommandContainer.
For example, the following sequence of entries would be illegal for a
CommandContainer:
FixedValueEntry-ContainerRefEntry-ParameterRefEntry-ArgumentRefEntry.
Unless there is a legitimate reason for the separation, I think the
FixedValueEntry and the ArgumentRefEntry needs to be added to the same
grouping that the ParameterRefEntry/ContainerRefEntry is in.

You're probably right. We simply extended the EntryListType to create a
CommandEntryList type. While this keeps the schema simpler, it does make
the XML documents messier. We usually opt for better XML over better
Schema.

This is a legacy issue during XTCE 1.0 modifications for XTCE 1.1

It appears that this issue was corrected in XTCE 1.1 and is probably here because of a database transition issue. Propose to close without change in the context of XTCE 1.2.