I think in this case you should engage rampart programmatically from your client code. Engaging in the conf file is not the right solution.
call axis2_svc_client_engage_module(svc_client, env, "rampart"); to engage it programmatically. For the secure case, create svc_client engage rampart set policy call svc_client send_receive For the non-secure case create svc_client call svc_client send_receive -Manjula. On Mon, 2009-03-09 at 20:41 -0700, Raymond Zhou wrote: > Hi Manjula, > > Maybe my writing is a bit confusing, my question is not really about > setting the policy file programmatically, my question is about how I > know the ws-security is enabled programmatically (which means that > the rampart/c module is engaged in axis2/c configuration file). I need > to know this because my client code need to support both ws-security > enabled and ws-security disabled (the normal case), so that in the > case of no ws-security I don't have to read the policy file and set > any ws-securit related parameters programmatically. > > Thanks! > Ray > > --- On Tue, 3/10/09, Manjula Peiris <[email protected]> wrote: > > > From: Manjula Peiris <[email protected]> > Subject: Re: How do I know ws-security is enabled > programmatically? > To: "Apache AXIS C User List" <[email protected]> > Date: Tuesday, March 10, 2009, 3:12 AM > > when you engage rampart there should be a policy to construct > the > message. Please see Rampart/c samples for more info. > > On Mon, 2009-03-09 at 00:20 -0700, Raymond Zhou wrote: > > > > A quick question. I am using rampart/c to provide > ws-security for a > > web service client application. How do I know ws-security is > enabled > > programmatically? I understand that in order to use > ws-security I need > > to do something in the configuration file axis2.xml and I > also need to > > put rampart/c as a module. But I also need to set the > security policy > > into the web service client object programmatically, right? > Then I > > need to know whether or not ws-security is enabled, and if > not, I > > don't need to set the policy (there is none actually) into > the ws > > client object. > > > > Thanks! > > Ray > > > > >
