RE: rampart_handler_util.c -- parameter not set

2008-10-04 Thread Manjula Peiris
> > From: Manjula Peiris [mailto:[EMAIL PROTECTED] > Sent: Fri 10/3/2008 11:11 PM > To: Apache AXIS C User List > Subject: RE: rampart_handler_util.c -- parameter not set > > > > > On Fri, 2008-10-03 at 22:43 -0400, Raghu Udupa wrote: > > Thanks, Shankar, f

RE: rampart_handler_util.c -- parameter not set

2008-10-04 Thread Raghu Udupa
11:11 PM To: Apache AXIS C User List Subject: RE: rampart_handler_util.c -- parameter not set On Fri, 2008-10-03 at 22:43 -0400, Raghu Udupa wrote: > Thanks, Shankar, for the explanation. I was trying to send a signed request > and receive a clear (un-signed) response. > > Our

RE: rampart_handler_util.c -- parameter not set

2008-10-03 Thread Manjula Peiris
programmatically. > > Regards, > > Raghu > > > > > From: Uthaiyashankar [mailto:[EMAIL PROTECTED] > Sent: Fri 10/3/2008 10:07 PM > To: Apache AXIS C User List > Subject: Re: rampart_handler_util.c -- parameter not set > > > > Hi Raghu, > >

RE: rampart_handler_util.c -- parameter not set

2008-10-03 Thread Raghu Udupa
gt; === > > > ReceiveEasyLinkFaxService > ReceiveEasyLinkFaxService Service > > > > > xmlns:rampc="http://ws.apache.org/rampart/c/policy";> > /usr/certdir/openssl_crt.pem ertificate> > > > Thanks, > Raghu > >

Re: rampart_handler_util.c -- parameter not set

2008-10-03 Thread Uthaiyashankar
IL PROTECTED] Sent: Thursday, October 02, 2008 1:13 PM To: Apache AXIS C User List Subject: Re: rampart_handler_util.c -- parameter not set Raghu Udupa wrote: Thanks Samisa. The first reported error is parameter 0 not being set in rampart_handler_util.c. I wanted to know which c

RE: rampart_handler_util.c -- parameter not set

2008-10-03 Thread Raghu Udupa
u -Original Message- From: Uthaiyashankar [mailto:[EMAIL PROTECTED] Sent: Thursday, October 02, 2008 1:13 PM To: Apache AXIS C User List Subject: Re: rampart_handler_util.c -- parameter not set Raghu Udupa wrote: > Thanks Samisa. > > The first reported error is par

Re: rampart_handler_util.c -- parameter not set

2008-10-02 Thread Uthaiyashankar
-- parameter not set 2. Also, the webservices client is getting following error while attempting to engage rampart module. [Wed Oct 1 11:36:33 2008] [error] rampart_handler_util.c(241) [rampart][rampart_handler_utils] 0 parameter is not set. [Wed Oct 1 11:36:33 2008] [warning

RE: rampart_handler_util.c -- parameter not set

2008-10-02 Thread Raghu Udupa
[mailto:[EMAIL PROTECTED] Sent: Wednesday, October 01, 2008 9:32 PM To: Apache AXIS C User List Subject: Re: rampart_handler_util.c -- parameter not set > > >2. Also, the webservices client is getting following error while > attempting to engage rampart module. > > [Wed Oc

Re: rampart_handler_util.c -- parameter not set

2008-10-01 Thread Samisa Abeysinghe
Raghu Udupa wrote: Hi, I modified axis2.xml to include Security phase in outflow phase order. That allowed the web services client to attempt rampart module. I am using axis2_http_server for doing the testing. 1. Is it OK to include security phase in axis2.xml when the client