Hello!
Thanx. I wrote an interceptor what clear the SoapHeader, and put before
the MAPCodec interceptor. And Its working.
thanx
Csaba
On 2018-11-01 19:31, Daniel Kulp wrote:
You likely will need to write an interceptor for the client that removes all
the WS-Addressing headers from the response prior to the correlation being done.
Dan
On Oct 31, 2018, at 8:31 AM, Tóth Csaba <[email protected]> wrote:
Hello!
Thanx, Ok.
I understand, But, I dont have any control of the service. So If the service
dont send the correct message Id back, I cant do nothing.
I'd like to turn off the response side addressing features. (I send out a
message and I'd like to get response even if the addressing is incorrect)
(but still in the request side i need the addressing thing, because the service
check it)
Thanx.
Csaba
Ps: I use sync webservices.
On 2018-10-31 11:49, Colm O hEigeartaigh wrote:
Here you can see that the "RelatesTo" ID returned by the service does not
match the original "MessageID" sent by the client, and so CXF throws an
exception as expected.
Colm.
On Tue, Oct 30, 2018 at 2:52 PM Tóth Csaba <[email protected]> wrote:
Hello!
Request header:
<soap:Header>
<Action soap:mustUnderstand="true"
xmlns="http://www.w3.org/2005/08/addressing
">urn:hl7-org:v3:PRPA_IN201305UV02</Action>
<MessageID
xmlns="http://www.w3.org/2005/08/addressing
">urn:uuid:acdd5cd4-1b7d-4027-b8a5-5b269c488d56</MessageID>
<To soap:mustUnderstand="true"
xmlns="http://www.w3.org/2005/08/addressing">
http://localhost:8085/mesa/test</To>
<ReplyTo xmlns="http://www.w3.org/2005/08/addressing">
<Address>http://schemas.xmlsoap.org/ws/2003/03/addressing/role/anonymous
</Address>
</ReplyTo>
<From xmlns="http://www.w3.org/2005/08/addressing">
<Address>http://schemas.xmlsoap.org/ws/2003/03/addressing/role/anonymous
</Address>
</From>
</soap:Header>
Response header:
<env:Header>
<wsa:To>http://localhost:8085/mesa/test</wsa:To>
<wsa:Action>urn:hl7-org:v3:PRPA_IN201306UV02</wsa:Action>
<wsa:MessageID>uuid:1.2.3.4.5.11312R1</wsa:MessageID>
<wsa:RelatesTo>uuid:d00e3a83-7d95-499e-a1b5-c8da600bbbf2.1</wsa:RelatesTo>
</env:Header>
Thanx
Csaba
On 2018-10-30 15:22, Colm O hEigeartaigh wrote:
What do the request and response messages look like?
Colm.
On Tue, Oct 30, 2018 at 1:11 PM Tóth Csaba <[email protected]>
wrote:
Hello!
I tried to write a we client. I need to send addressing info (its
already working), but it cant parse the response:
the error:
WARN org.apache.cxf.ws.addressing.soap.MAPCodec - Failed to
correlate message, aborting dispatch.
And the proxy response object is become null.
At the response there is an addressing: "<To>" but its pointed to the
server's address. ( I dont know its right value or not)
How can I fix this warning, or turn off the addressing handling only for
the responses?
Thanx
Csaba