rte
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
Date: Fri, 5 Aug 2011 13:57:54 -0400
Subject: Re: Having trouble interfacing with WCF
From: not...@gmail.com
To: ja
On Fri, Aug 5, 2011 at 12:34 PM, Hasini Gunasinghe wrote:
> Hi Jay,
>
> Since you've generated stubs from a security policy annotated wsdl, you do
> not need to load the security policy from file in the client side.
>
> But you need to set the rampart specific configurations in the client side.
>
Hi Jay,
Since you've generated stubs from a security policy annotated wsdl, you do
not need to load the security policy from file in the client side.
But you need to set the rampart specific configurations in the client side.
The article that I pointed in my previous mail describes how to do it
p
On Thu, Aug 4, 2011 at 8:46 PM, Martin Gainty wrote:
> in policy.xml set your stsAlias element in RampartConfig parent e.g:
>
> http://ws.apache.org/rampart/policy";>
> sts
>
> Martin
>
I don't understand, I don't have a policy.xml. I'm pretty sure WsImport
automatica
responsabilité
pour le contenu fourni.
Date: Thu, 4 Aug 2011 16:06:24 -0400
Subject: Re: Having trouble interfacing with WCF
From: not...@gmail.com
To: java-dev@axis.apache.org
Okay, so, I think I may have gotten it to work now. It's weird because, at
first, I could have sworn I tried this
Since I've gotten *WSS SOAP Message Security UsernameToken Profile 1.0* to
work (at least on Linux), I decided to share with others the complete,
fool-proof, list of steps describing what I did to get it to work, from
scratch. I hope the formatting in this email doesn't cause readability
issues (
Okay, so, I think I may have gotten it to work now. It's weird because, at
first, I could have sworn I tried this many times and it did not work.
Suddenly it's working. I think what I did differently is include the
rampart JAR files in the classpath while I run the client. This works for
axis2-1
On Thu, Aug 4, 2011 at 11:41 AM, Martin Gainty wrote:
> here is a dirt simple ServiceClient that works with rampart engaged
> ...
>
> ServiceClient client = new ServiceClient(ctx, null);
> Options options = new Options();
> options.setAction("urn:echo");
> options
rdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
Date: Thu, 4 Aug 2011
On Thu, Aug 4, 2011 at 9:57 AM, Jay Sullivan wrote:
>
>
> On Wed, Aug 3, 2011 at 9:22 PM, Hasini Gunasinghe wrote:
>
>> Hi Jay,
>>
>> Have you engaged Rampart, and provided the rampart configuration properly
>> in the Axis2 client side?
>>
>> You can refer to rampart samples[1] to verify this.
>>
On Wed, Aug 3, 2011 at 9:22 PM, Hasini Gunasinghe wrote:
> Hi Jay,
>
> Have you engaged Rampart, and provided the rampart configuration properly
> in the Axis2 client side?
>
> You can refer to rampart samples[1] to verify this.
> Also, the article[2] on message level security with Rampart may hel
Hi Jay,
Have you engaged Rampart, and provided the rampart configuration properly in
the Axis2 client side?
You can refer to rampart samples[1] to verify this.
Also, the article[2] on message level security with Rampart may help.
[1]
http://svn.apache.org/repos/asf/axis/axis2/java/rampart/trunk/
Hi,
I'm trying to create an Axis2 Web Service Client that consumes a WCF
Service, and pass it a username and password so that the WCF service can run
as a specified authenticated user.
Of all of WCF's supported supposedly-interoperable protocols (listed at
http://msdn.microsoft.com/en-us/library/
13 matches
Mail list logo
