You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by to...@web.de on 2023/03/21 15:37:20 UTC
How to enable WSAddressingFeature
Hi,
we use TomEE 8.0.14 with CXF.
in the resouces/META-INF/resources we have following line:
<resources>
<!-- Features -->
<Service id="addressingFeature" class-name="org.apache.cxf.ws.addressing.WSAddressingFeature"/>
</resources>
Further in the same folder the openejb-jar.xml has following entry:
<openejb-jar xmlns="http://www.openejb.org/openejb-jar/1.1">
<ejb-deployment ejb-name="CustomerWebService"> <!-- configure the bean, values are in resources.xml -->
<properties>
cxf.jaxws.features = addressingFeature
cxf.jaxws.debug = true
</properties>
</ejb-deployment>
</openejb-jar>
I was assuming that the WS address feature on the server is enabled and the SOAP response get an ReplyTo Header.
But the header the Reply-To Header. [1]
Expexting I was this Sreponse. [2]
How can I enable with TomEE WS-Addressing with CXF?
Thanks,
Markus
[1]
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<Action xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">urn:getCustomerResponse</Action>
<MessageID xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">urn:uuid:0ecf3478-7e43-4f92-b577-03e2c26ea967</MessageID>
<To xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</To>
<RelatesTo xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">uuid:2af7a1b0-5938-44d0-9644-d96c64718b1d</RelatesTo>
<axis2:ServiceGroupId xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:axis2="http://ws.apache.org/namespaces/axis2" xmlns:ns1="http://wibu.com/wsutil/"
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsa:IsReferenceParameter="1">
urn:uuid:946dce7ef3b641b2b07a3fbd37c33bf
</axis2:ServiceGroupId>
</soap:Header>
<soap:Body>
[...]
</soap:Body>
</soap:Envelope>
[2]
<?xml version="1.0" encoding="utf-8"?><soapenv:Envelope xmlsoapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header xmlwsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
<ServiceGroupId xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">urn:uuid:c5b7b50bba3d4552978c4615ec9c793</ServiceGroupId>
<wsa:To>http://www.w3.org/2005/08/addressing/anonymous</wsa:To>
<wsa:ReplyTo>
<wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address>
<wsa:ReferenceParameters>
<axis2:ServiceGroupId xmlaxis2="http://ws.apache.org/namespaces/axis2">urn:uuid:d0263a1c-8b26-4f18-9379-e0c573e1a399</axis2:ServiceGroupId>
</wsa:ReferenceParameters>
</wsa:ReplyTo>
<wsa:MessageID>urn:uuid:7eded005-f9a4-4a4e-99c0-b027b56471a6</wsa:MessageID>
<wsa:Action>urn:getCustomerResponse</wsa:Action>
<wsa:RelatesTo>6a045fc6-1a29-4990-b209-be023d06e4bc</wsa:RelatesTo>
</soapenv:Header>
<soapenv:Body>
[...]
</soapenv:Body>
</soapenv:Envelope>