Uploaded image for project: 'Axiom'
  1. Axiom
  2. AXIOM-119

Attachment order is not preserved in Axiom

    Details

    • Type: Bug
    • Status: Closed
    • Priority: 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.

        Attachments

          Activity

            People

            • Assignee:
              scheu@us.ibm.com Rich Scheuerle
              Reporter:
              scheu@us.ibm.com 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