[jira] Resolved: (WSCOMMONS-477) Attachment order is not preserved in Axiom

["Rich Scheuerle (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WSCOMMONS-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rich Scheuerle resolved WSCOMMONS-477.
--------------------------------------

    Resolution: Fixed

Committed revision 785554

Kudos to Tim Mitchell (IBM) for finding this issue and providing verification.

> Attachment order is not preserved in Axiom 
> -------------------------------------------
>
>                 Key: WSCOMMONS-477
>                 URL: https://issues.apache.org/jira/browse/WSCOMMONS-477
>             Project: WS-Commons
>          Issue Type: Bug
>          Components: AXIOM
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Scenario;
> 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.
> Problem:
> 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.
> Solution:
> I am working on a small change and accompanying test to allow Axiom to preserve the attachment order.   

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.