Axiom reads an inbound message message containing attachments.
Axiom writes the message so that it can be sent to another service.
The remote service fails because the attachments are sent in the wrong order.
The order of the attachments is not preserved. In most cases, this is not an issue because the receiving service will use mtom, swaref or other references to obtain the attachment information. However some older style SWA implementations or legacy vendors do rely on the attachment order.
I am working on a small change and accompanying test to allow Axiom to preserve the attachment order.