!
> Vivian
>
>
> --- On Tue, 11/4/08, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote:
>
> > From: Samisa Abeysinghe <[EMAIL PROTECTED]>
> > Subject: Re: What are the configurable ws-security parameters for incoming
> > message
> > To: "Apache AXIS
]>
Subject: Re: What are the configurable ws-security parameters for incoming
message
To: "Apache AXIS C Developers List"
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Date: Tuesday, November 4, 2008, 10:59 PM
Rampart/C makes use of WS-Policy for configuring how it
behaves.
Samisa...
aves.
>
> Samisa...
>
> Vivian Wang wrote:
> > Hi,
> >
> > I am trying to use rampart/c along with axis2/c to
> support WS-security. Just wonder, what are the configurable
> ws-security parameters for incoming message, especially from
> a web service clien
Rampart/C makes use of WS-Policy for configuring how it behaves.
Samisa...
Vivian Wang wrote:
Hi,
I am trying to use rampart/c along with axis2/c to support WS-security. Just
wonder, what are the configurable ws-security parameters for incoming message,
especially from a web service client
Hi,
I am trying to use rampart/c along with axis2/c to support WS-security. Just
wonder, what are the configurable ws-security parameters for incoming message,
especially from a web service client point of view, which means, as a web
service client, what can be configured to decrypt/interpret
