[
https://issues.apache.org/jira/browse/WSCOMMONS-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720631#action_12720631
]
Andreas Veithen commented on WSCOMMONS-477:
-------------------------------------------
Rich,
What is the reason to make this configurable? Why wouldn't we always write the
attachments in the order they have been added (or read)? I don't see any
situation where writing the attachments in random order (determined by the
internals of HashMap or HashSet) would make sense.
> 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.
