Axiom
  1. Axiom
  2. AXIOM-119

Attachment order is not preserved in Axiom

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.2.9
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Activity

        Andreas Veithen made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Jeff Turner made changes -
        Fix Version/s Axiom 1.2.9 [ 12315532 ]
        Andreas Veithen made changes -
        Project WS-Commons [ 12310250 ] Axiom [ 12311190 ]
        Key WSCOMMONS-477 AXIOM-119
        Component/s AXIOM [ 12310703 ]
        Fix Version/s Axiom 1.2.9 [ 12313561 ]
        Davanum Srinivas made changes -
        Status Reopened [ 4 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Andreas Veithen made changes -
        Resolution Fixed [ 1 ]
        Status Resolved [ 5 ] Reopened [ 4 ]
        Andreas Veithen made changes -
        Fix Version/s Axiom 1.2.9 [ 12313561 ]
        Rich Scheuerle made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Rich Scheuerle created issue -

          People

          • Assignee:
            Rich Scheuerle
            Reporter:
            Rich Scheuerle
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 48h
              48h
              Remaining:
              Remaining Estimate - 48h
              48h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Development