ipient. Sender does not
necessarily endorse content contained within this transmission.
--------------------
Date: Wed, 3 Sep 2008 20:11:56 +0200
From: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
To: axis-user@ws.apache.
0200
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Subject: Re: *SPAM* Re: *SPAM* RE: *SPAM* RE: Problem verifying the signature
with wss4j... Good News!!
Because I had no time enough to make the entire development with the
right certificate, I'm still waiting for it and this
Because I had no time enough to make the entire development with the
right certificate, I'm still waiting for it and this should be finnished
on friday... That's why I wanted to have some code(altough I was not
gonna work), and then had something prepared for the right certificate.
Then, in thi
Correct Frank,
Why don't you get the right certificate you need that is issued and signed
by the correct third party?
Un saludo.
José
On Wed, Sep 3, 2008 at 7:09 PM, Tomás Tormo <[EMAIL PROTECTED]> wrote:
> Good news!!! After changing the keystore for "interop2.jks", and using
> "alice" as ali
Good news!!! After changing the keystore for "interop2.jks", and using
"alice" as alias the exception changed :). Now it looks like this:
WSDoAllReceiver: The certificate used for the signature is not trusted
I'm trying the webservice client against a public webservice, that's why
I think t
Sorry, my mistake, the client_deploy.wsdd file I'm using is the
following one:
http://xml.apache.org/axis/wsdd/";
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
pivot="java:org.apache.axis.transport.http.HTTPSender"/>
type="java:org.apache.ws.axis.security.WSDoAllSender" >
