camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <>
Subject Re: Camel CXF Proxy with WS-Security
Date Tue, 25 Mar 2014 01:47:22 GMT

Is it JUST the namespace that needs to be changed?  One option would be to have CXF do that
while reading or writing messages by use CXF’s transform feature:

It’s primary purpose was to handle Namespace mapping and minor XML changes while reading
in messages or writing messages.   That could help simplify things a bit for you.


On Mar 24, 2014, at 10:39 AM, chaij <> wrote:

> I don't really know what needs to done with the Camel message headers. I
> couldn't find documentation on how to use CXF_MESSAGE. I think that's the
> issue.
> When I feed the soap envelope in string format to CXF endpoint, the SOAP
> body is empty when coming out the endpoint. 
> To recap what I need:
> proxy client ->CXF Endpoint->processor to modify namespace and values
> etc->CXF Endpoint with Security->Real Service
> I am stuck on the processor. How to process the incoming message and then
> feed it to the next CXF Endpoint in CXF_MESSAGE format since security is
> needed.
> Can some expert help out here?
> Thanks,
> Jin
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

Daniel Kulp -
Talend Community Coder -

View raw message