Uploaded image for project: 'Axis2'
  1. Axis2
  2. AXIS2-414

MTOM attachments is not interoperable with .Net

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.94
    • Fix Version/s: 0.95
    • Component/s: Integration
    • Labels:
      None
    • Environment:
      all

      Description

      I am starting to integrate some attachment processing into my webservices and found problem with MS [MS client/Axis2 server].

      .Net complains about WS-A messageID not being a valid URI.

      Here's a sample of what Axis2 sends:
      <wsa:MessageID xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">2B5D48043825641218113814178055274</wsa:MessageID>

      And here's a sample of what .Net expects:
      <wsa:MessageID>urn:uuid:2a5b38c2-c87a-4c10-9dd8-3753e2cbfefb</wsa:MessageID>

      This may be a WS-A spec interpretation issue, but it causes non-interop. Although, the WS-A spec does say that it must be a valid URI.

      The following is taken directly from the spec:
      wsa:MessageID
      This OPTIONAL element (of type xs:anyURI) conveys the [message id] property. This element MUST be present if wsa:ReplyTo or wsa:FaultTo is present.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              saspad Tony Dean

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment