In the mapping file, for the map of a specific class, I declare the fields (<field> tag) in the following order:
- destination
- message class
- message type
- message id
- message body
with the "message class", "message type" and "message id" fields using the location attribute, to generate a tag like
<MessageClass Value="XXXXX"/>.
After the marshall I get all the tags correctly, but the order I specified in the mapping was not followed, having the fields with the location attribute been written in the end:
- destination
- message body
- message class
- message type
- message id
Is there a way of preventing/resolving this?
Part of the mapping I'm using is:
<field name="Destination">
<bind-xml name="Destination"/>
</field><field name="MsgClass" required="true">
<bind-xml name="Value" location="MessageClass" node="attribute"/>
</field>
<field name="MessageType" required="true">
<bind-xml name="Value" location="MessageType" node="attribute"/>
</field> <field name="MessageId" required="true">
<bind-xml name="Value" location="MessageID" node="attribute"/>
</field><field name="MsgBody" required="true" type="com.otlis.messias.message.common.SIITMessageBody">
<bind-xml auto-naming="deriveByClass" node="element"/>
</field>
Thank you in advance,
--Renato
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
