AssignMessage Child Element Ordering

[roberthoppe]

Hi guys,

is the ordering of Elements in an AssignMessage relevant for its execution?

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<AssignMessage name="AM-Token" enabled="true" continueOnError="false">
    <Remove>
        <Headers>
            <Header name="Authorization"/>
        </Headers>
    </Remove>
    <Add>
        <Headers>
            <Header name="Authorization">Bearer {private.cached.my_access_token}</Header>
        </Headers>
    </Add>
    <AssignTo createNew="true" transport="http" type="request"/>
    <IgnoreUnresolvedVariables>true</IgnoreUnresolvedVariables>
</AssignMessage>

vs.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<AssignMessage name="AM-Token" enabled="true" continueOnError="false">
    <Add>
        <Headers>
            <Header name="Authorization">Bearer {private.cached.my_access_token}</Header>
        </Headers>
    </Add>
    <Remove>
        <Headers>
            <Header name="Authorization"/>
        </Headers>
    </Remove
    <AssignTo createNew="true" transport="http" type="request"/>
    <IgnoreUnresolvedVariables>true</IgnoreUnresolvedVariables>
</AssignMessage>

Brings a different result for me ... is that expected behaviour? Because I don't find something about ordering within the documentation.