[
https://issues.apache.org/jira/browse/WSCOMMONS-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722351#action_12722351
]
Davanum Srinivas commented on WSCOMMONS-477:
--------------------------------------------
Andreas,
I'd let Rich answer that specifically. My guess is that he wants to preserve
existing behavior as-is till we hit say Axiom 1.3. we may be being a bit more
paranoid than required :)
-- dims
> 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
> Fix For: Axiom 1.2.9
>
> 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.
