cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] [Resolved] (CXF-7395) WS-Addressing issue related to WS-RM when using SoapUI
Date Wed, 07 Jun 2017 17:58:18 GMT


Daniel Kulp resolved CXF-7395.
    Resolution: Fixed
      Assignee: Daniel Kulp

I've "fixing" this, but really this is a bug in SOAP UI.

The WS-Addressing spec states specifically:

Comparison of [destination] property values is out of scope, other than using simple string
comparison to detect whether the value is anonymous, that is, where [destination] has the
value ""

so the simple string comparison of the exact value should work.   

> WS-Addressing issue related to WS-RM when using SoapUI
> ------------------------------------------------------
>                 Key: CXF-7395
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 3.1.7, 3.1.10
>            Reporter: Hadrian Zbarcea
>            Assignee: Daniel Kulp
>            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):
> {code}
>   <soap:Body>
>     <CreateSequence xmlns="" xmlns:ns2="">
>       <AcksTo>
>         <ns2:Address></ns2:Address>
>       </AcksTo>
>       <Expires>PT0S</Expires>
>       <Offer>
>         <Identifier>urn:uuid:d4bbc349-7844-4ed4-b35c-de4231f2e032</Identifier>
>         <Endpoint>
>           <ns2:Address></ns2:Address>
>         </Endpoint>
>         <Expires>PT0S</Expires>
>       </Offer>
>     </CreateSequence>
>   </soap:Body>
> </soap:Envelope>
> {code}
> If other clients are used, such as SoapUI, the message is generated slightly differently:
> {code}
>   <soapenv:Body xmlns:wsrm="">
>     <wsrm:CreateSequence>
>       <wsrm:AcksTo xmlns:wsa="">
>         <wsa:Address></wsa:Address>
>       </wsrm:AcksTo>
>     </wsrm:CreateSequence>
>   </soapenv:Body>
> {code}
> The issue is with the {{<wsa:Address>}} element, that is not an exact match to
{{}}, but it contains an extra query parameter:
>  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 fixing.

This message was sent by Atlassian JIRA

View raw message