cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadrian Zbarcea (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-7395) WS-Addressing issue related to WS-RM when using SoapUI
Date Wed, 07 Jun 2017 18:14:18 GMT

    [ https://issues.apache.org/jira/browse/CXF-7395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16041354#comment-16041354
] 

Hadrian Zbarcea commented on CXF-7395:
--------------------------------------

Thanks [~dkulp] ! Fully agree about being a bug in SoapUI. That's why the issue is minor.
Unfortunately the workaround is not well documented. Your fix will simplify the lives of a
few developers, much appreciated.  

> WS-Addressing issue related to WS-RM when using SoapUI
> ------------------------------------------------------
>
>                 Key: CXF-7395
>                 URL: https://issues.apache.org/jira/browse/CXF-7395
>             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="http://docs.oasis-open.org/ws-rx/wsrm/200702" xmlns:ns2="http://www.w3.org/2005/08/addressing">
>       <AcksTo>
>         <ns2:Address>http://www.w3.org/2005/08/addressing/anonymous</ns2:Address>
>       </AcksTo>
>       <Expires>PT0S</Expires>
>       <Offer>
>         <Identifier>urn:uuid:d4bbc349-7844-4ed4-b35c-de4231f2e032</Identifier>
>         <Endpoint>
>           <ns2:Address>http://www.w3.org/2005/08/addressing/anonymous</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="http://docs.oasis-open.org/ws-rx/wsrm/200702">
>     <wsrm:CreateSequence>
>       <wsrm:AcksTo xmlns:wsa="http://www.w3.org/2005/08/addressing">
>         <wsa:Address>http://www.w3.org/2005/08/addressing/anonymous?id=0cbf2f7c-0e91-49b3-90d2-68219df51735</wsa:Address>
>       </wsrm:AcksTo>
>     </wsrm:CreateSequence>
>   </soapenv:Body>
> {code}
> The issue is with the {{<wsa:Address>}} element, that is not an exact match to
{{http://www.w3.org/2005/08/addressing/anonymous}}, 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 fixing.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message