Hi, I think you need to build the soap envelop yourself before send the request message (without security headers)in the camel route, then let the CXF security interceptor do the other work for you when routing the message out to the camel route.
-- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On March 23, 2014 at 10:46:15 PM, chaij (jin.c...@indigoarc.com) wrote: > it does seem to work by feeding the soap string to the cxf client. > I fixed the namespace. > I wonder if anything that needs to done to the camel message header. > > Is there an easier/right way to generate a request to a cxf component that > accepts CXF_MESSAGE? > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-CXF-Proxy-with-WS-Security-tp5749223p5749256.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
