Yogesh,
Thank you for the info! It should work.
regards,
Anton
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-component-with-WS-Addressing-and-one-way-messages-tp4370106p4928987.html
Sent from the Camel - Users mailing list archive at Nabble.com.
.setHeader(Client.REQUEST_CONTEXT ,
requestContext);
}
Cheers,
Yogesh
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-component-with-WS-Addressing-and-one-way-messages-tp4370106p493.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi All,
It seems that that post is closest one to the subject I want to ask.
I use WS-addressing with Camel-CXF component. I send a request to a web-
service (configured as http://camel.465427.n5.nabble.com/CXF-component-with-WS-Addressing-and-one-way-messages-tp4370106p4865074.html
Sent from
.465427.n5.nabble.com/CXF-component-with-WS-Addressing-and-one-way-messages-tp4370106p4373076.html
Sent from the Camel - Users mailing list archive at Nabble.com.
h, I am wondering why
there is a reply. Any ideas?
Thanks,
Yogesh
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-component-with-WS-Addressing-and-one-way-messages-tp4370106p4371753.html
Sent from the Camel - Users mailing list archive at Nabble.com.
exists.
I believe this is just a warning so it might simply be advisory, but did I
configure WS addressing incorrectly?
Thanks,
Yogesh
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-component-with-WS-Addressing-and-one-way-messages-tp4370106p4370106.html
Sent from the Cam
