- Original Message
From: Sanka Samaranayke <[EMAIL PROTECTED]>
To: axis-dev@ws.apache.org
Sent: Wednesday, October 31, 2007 10:25:11 PM
Subject: Re: [Axis2] WS-policy client support
Hi,
One work around would be to use the ServiceClient instead of using a generated
stub and attach the equi
And pretty darned sneaky of them to gen a "wssp" prefix for a private
namespace. Of course its fine but still sneaky.
Sanjiva.
Anne Thomas Manes wrote:
That's a proprietary policy assertion language. It's supported only by
BEA products. Talk to BEA and convince them to add support for the
stan
Hi,
One work around would be to use the ServiceClient instead of using a generated stub and attach the equivalent standard policy of that proprietary policy expreesion.
You may also have to set username and password in options.
e.g.
Options options = serviceClient.getOptions();
options.setUs
That's a proprietary policy assertion language. It's supported only by
BEA products. Talk to BEA and convince them to add support for the
standard OASIS WS-SecurityPolicy.
Anne
On 10/31/07, Feng Lu <[EMAIL PROTECTED]> wrote:
>
> Hello friends,
>
> I am wondering whether Axis2 support WS-policy cl
Hello friends,
I am wondering whether Axis2 support WS-policy client? My WSDL server is
Weblogic and the WSDL has following WS-policy. I am not sure whether Axis2 will
be able to handle WS-policy in such case. If it does, could anybody let me know
how to implement the client side support for th
