I don't think that you can provide this property as a parameter in cxf://someAddress? WSS4JInInterceptor=xxxx. It must be declarer as you can see in my example using spring bean.
On Fri, Jun 10, 2011 at 8:46 AM, Mark Borner <mark.bor...@zurich.com.au>wrote: > > Thanks for that. > > Is there anyway to add the WSS4JInInterceptor to the endpoint if I'm using > cxf://someAddress[?options] instead of the cxf:bean:cxfEndpoint endpoint > definition? > > Thanks, > Mark > > Mark Borner > Java Developer - ZStream Xpress > > > From: Charles Moulliard <cmoulli...@gmail.com> To: users@camel.apache.org > Date: 10/06/2011 04:23 PM Subject: Re: Camel CXF & WS-Security > ------------------------------ > > > > Hi Mark, > > I have created one year an example in camel project available here : > > > https://github.com/gnodet/camel/tree/trunk/examples/camel-example-reportincident-ws-security-osgi > > Regards, > > Charles Moulliard > > Apache Committer > > Blog : http://cmoulliard.blogspot.com > Twitter : http://twitter.com/cmoulliard > Linkedin : http://www.linkedin.com/in/charlesmoulliard > Skype: cmoulliard > > > On Fri, Jun 10, 2011 at 6:22 AM, Mark Borner <mark.bor...@zurich.com.au > >wrote: > > > > > Does anyone have any examples of how to configure a Camel CXF endpoint to > > use WS-Security? I need to secure an outbound and inbound SOAP message. > > > > Thanks, > > Mark > > > > Mark Borner > > Java Developer - ZStream Xpress > > > > > > > > > > ---- > > This email is intended for the named recipient only. It may contain > > information which is confidential, commercially sensitive, or > > copyright. If you are not the intended recipient you must not > > reproduce or distribute any part of the email, disclose its contents, > > or take any action in reliance. If you have received this email in > > error, please contact the sender and delete the message. It is your > > responsibility to scan this email and any attachments for viruses and > > other defects. To the extent permitted by law, Zurich and its > > associates will not be liable for any loss or damage arising in any > > way from this communication including any file attachments. We may > > monitor email you send to us, either as a reply to this email or any > > email you send to us, to confirm our systems are protected and for > > compliance with company policies. Although we take reasonable > > precautions to protect the confidentiality of our email systems, we > > do not warrant the confidentiality or security of email or > > attachments we receive. > > > > > > > > > > > ---- > This email is intended for the named recipient only. It may contain > information which is confidential, commercially sensitive, or > copyright. If you are not the intended recipient you must not > reproduce or distribute any part of the email, disclose its contents, > or take any action in reliance. If you have received this email in > error, please contact the sender and delete the message. It is your > responsibility to scan this email and any attachments for viruses and > other defects. To the extent permitted by law, Zurich and its > associates will not be liable for any loss or damage arising in any > way from this communication including any file attachments. We may > monitor email you send to us, either as a reply to this email or any > email you send to us, to confirm our systems are protected and for > compliance with company policies. Although we take reasonable > precautions to protect the confidentiality of our email systems, we > do not warrant the confidentiality or security of email or > attachments we receive. > >
