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.
Hi Anton,
Here is how you set the message ID:
String requestID = "MY_MESSAGE_ID"
if (StringUtils.isNotEmpty(requestID))
{
// get Message Addressing Properties instance
AddressingBuilder
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 the
Well, this might not be an issues for the Camel mailing list. I downloaded
cxf 2.4.0 and 2.2.12 and ran the WS Addressing samples distributed with them
and saw the same behavior. I bumped this message over to the CXF mailing
list.
Thanks,
yogesh
--
View this message in context:
http://camel.4
An upgrade to version 2.2.12 corrected the exception, but brought up another
one...
I am calling a one-way service but a response is being sent back. For
example:
http://www.w3.org/2003/05/soap-envelope";>
http://www.w3.org/2005/08/addressing";>urn:uuid:b8d0a8ca-ada1-4840-8722-a4859144
