[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xmlrpc-user
Subject:    [jira] [Commented] (AXIOM-119) Attachment order is not preserved in
From:       "Hudson (JIRA)" <jira () apache ! org>
Date:       2011-07-30 15:06:09
Message-ID: 1483094515.20906.1312038369626.JavaMail.tomcat () hel ! zones ! apache ! org
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/AXIOM-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073194#comment-13073194 \
] 

Hudson commented on AXIOM-119:
------------------------------

Integrated in ws-axiom-trunk #463 (See \
[https://builds.apache.org/job/ws-axiom-trunk/463/])  AXIOM-119: Always preserve the \
order of attachments (which was already the default behavior since r785554). There is \
no use case where the pre-r785554 behavior (i.e. sorting attachments by content ID) \
would be mandatory [1], and removing support for this frees us from the constraint of \
maintaining two collections with different orders in the Attachments class.

[1] XOP explicitly specifies that the order of MIME parts is irrelevant. The same \
should be true for SwA messages using swaRef. Finally, for services described using \
the WSDL MIME binding, preserving the order of attachments is mandatory.

veithen : 
Files : 
* /webservices/commons/trunk/modules/axiom/modules/axiom-api/src/main/java/org/apache/axiom/om/impl/MIMEOutputUtils.java
                
* /webservices/commons/trunk/modules/axiom/modules/axiom-api/src/main/java/org/apache/axiom/om/OMOutputFormat.java
                
* /webservices/commons/trunk/modules/axiom/modules/axiom-tests/src/test/java/org/apache/axiom/attachments/AttachmentsTest.java



> Attachment order is not preserved in Axiom 
> -------------------------------------------
> 
> Key: AXIOM-119
> URL: https://issues.apache.org/jira/browse/AXIOM-119
> Project: Axiom
> Issue Type: Bug
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Fix For: 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]