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

MessageIDs for WS-Addressing are not valid (absolute) URIs

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 0.94
    • Fix Version/s: 0.95
    • Component/s: Integration, kernel
    • Labels:
      None
    • Environment:
      Windows XP Pro, JBoss 3.2.3

      Description

      An example of Axis2 generated MessageID: 88CCBC8E1CDD11F42711392097914632.

      This causes interoperability issues when a .NET client (tested with WSE 3.0) tries to call an Axis2 web service with WS-Addressing enabled. The .NET client expects the MessageID to be in a valid (absolute) URI format, eg. uuid:aaaabbbb-cccc-dddd-eeee-wwwwwwwww (according to section 3.2 of WS-Addressing spec 20040810)

      SUGGESTED RESOLUTION:
      ----------------------------------------------------------------
      The affected Java classes are:
      1. org.apache.axis2.util.Utils. Change:
      newmsgCtx.setMessageID(UUIDGenerator.getUUID());
      to:
      newmsgCtx.setMessageID("uuid:" + UUIDGenerator.getUUID());

      2. org.apache.axis2.description.OutInAxisOperationClient. Change:
      messageId = UUIDGenerator.getUUID();
      to:
      messageId = "uuid:" + UUIDGenerator.getUUID();

      3. org.apache.axis2.description.OutOnlyAxisOperationClient. Change:
      messageId = UUIDGenerator.getUUID();
      to:
      messageId = "uuid:" + UUIDGenerator.getUUID();

      NOTE:
      ----------------------------------------------------------------
      This is indirectly related to issue AXIS2-92

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              juandazeng Juanda Zeng
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: