Problems with 1:n mappings

[Leandro Augusto de Almeida]

I'm having problems using 1:n mapping bi-directional relationship with
more than one element inverse foreignkey.
It seems that the order of elements in the repository is changing the
behavior of the broker.
EX:   <collection-descriptor
         name=...
         element-class-ref=...
         auto-retrieve="true"
         auto-update="true"
         auto-delete="false"
      >
         <inverse-foreignkey field-ref="A"/>
         <inverse-foreignkey field-ref="B"/>
         <inverse-foreignkey field-ref="C"/>
      </collection-descriptor>
 
If I change the order of inverse-foreignkey it results in different
cases: 1. Runtime Error (null reference), 2. Wrong data retrieve, 3. The
right data.
 
My question: Is the order really important? Am I doing something wrong?
 
Thanks,
 
Leandro Augusto de Almeida.