cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadrian Zbarcea (JIRA)" <>
Subject [jira] [Created] (CXF-7395) WS-Addressing issue related to WS-RM when using SoapUI
Date Mon, 05 Jun 2017 20:35:04 GMT
Hadrian Zbarcea created CXF-7395:

             Summary: WS-Addressing issue related to WS-RM when using SoapUI
                 Key: CXF-7395
             Project: CXF
          Issue Type: Bug
          Components: WS-* Components
    Affects Versions: 3.1.10, 3.1.7
            Reporter: Hadrian Zbarcea
            Priority: Minor
             Fix For: 3.2.0, 3.1.12

When using WS-RM the first out-of-band message is necessary to generate a sequence identifier.
CXF WS-RM implementation uses a message of the following form (and everything works):

    <CreateSequence xmlns="" xmlns:ns2="">

If other clients are used, such as SoapUI, the message is generated slightly differently:

  <soapenv:Body xmlns:wsrm="">
      <wsrm:AcksTo xmlns:wsa="">

The issue is with the {{<wsa:Address>}} element, that is not an exact match to {{}},
but it contains an extra query parameter: {{?id=0cbf2f7c-0e91-49b3-90d2-68219df51735}}.
 CXF however tests for an exact match.

This is not a major issue, as there is an undocumented workaround to explicitly set the {{Acknowledgement
to:}} field in the WS-RM field in SoapUI to the exact value of the ws-a anonymous url. However,
given CXF's tradition of being strict with itself and lenient with other stacks, this is worth

This message was sent by Atlassian JIRA

View raw message