Ted, Dims, thanks for the answers.
First, the need for a basic tutorial is still needed. I still don't
understand how to use WSS4J, and I know there are others out there with the
same question. I'm in contact with lots of Swedish developers and solution
architects that are really interested in WSS4J, but we all need some help to
get into it. So please, a simple step-by-step thingy about how to create a
console app soap client that uses AXIS WSDL2JAVA stubs, that would be
perfect!
I would love to help out with a patch, but again, I need to get into
WSS4J first :) Tim, it sounds like you've know lots about this, can't you
write down a few simple steps? (Promise to buy you a pint of beer, coke or
whatever if we meet ;)
/Johan
-----Original Message-----
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: den 6 januari 2005 16:07
To: Ted Toth
Cc: Johan Danforth; [email protected]
Subject: Re: tutorials or walkthroughs?
Ted,
i will support you...but i don't know much :)
-- dims
On Thu, 6 Jan 2005 09:03:00 -0600, Ted Toth <[EMAIL PROTECTED]>
wrote:
> Dims,
> When I first raised this issue I offered help but explained that I
might
> need some direction and there was no response. I will revisit the
issue if
> you will support me.
>
> Ted
>
> -----Original Message-----
> From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
> Sent: Thursday, January 06, 2005 8:51 AM
> To: Ted Toth
> Cc: Johan Danforth; [email protected]
> Subject: Re: tutorials or walkthroughs?
>
> Ted,
>
> We're open to accepting patches :)
>
> -- dims
>
> On Thu, 6 Jan 2005 08:47:23 -0600, Ted Toth
<[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > Johan,
> >
> > Currently some compatibility issues exist with WSS4J and .Net WSE
2.0 for
> > example:
> >
> > The problem exists with signed messages coming from the Java SDK
to the
> .NET
> > SDK when dealing with a SAML Assertion that has been signed.
Microsoft
> > requires that the saml:AssertionID be the ID that is being used
when
> > referencing a signed element. Right now, the Java SDK adds a
wsu:Id based
> on
> > the WS-Security specification to reference the signed elements.
> >
> >
> >
> > I have tried unsuccessfully to generate interest in addressing
> > interoperability issues. However if enough of us show interest
maybe
> things
> > will start to happen.
> >
> >
> >
> > Ted
> >
> >
> >
> >
> >
> >
> >
> > ________________________________
> >
> >
> > From: Johan Danforth [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, January 06, 2005 6:37 AM
> > To: [email protected]
> > Subject: tutorials or walkthroughs?
> >
> >
> >
> >
> > Hi all,
> >
> > I would like to use WSS4J together with AXIS primarily to send
soap
> requests
> > with Usernametokens and Binarytokens to Web Services built with
ASP.NET
> and
> > WSE 2.0, but I'm new to WSS4J and I've only used AXIS to build
pretty
> simple
> > SOAP clients. I'm having a hard time understanding how to use
WSS4J, I've
> > tried a few things but it doesn't work at all.
> >
> > As I understand it there are 2 ways to define a handler for
adding
> > usernametoken, either through a client.wsdd file or do it
dynamically.
> I've
> > created a few AXIS web services before and understand the wsdd
files in
> > there, but how is that supposed to work with a soap client?
Besides, what
> > I'm most interested in is adding tokens dynamically in runtime,
because I
> > need to be able to set different usernames and stuff like that.
> >
> > I could paste in some code that I've tried, but maybe someone out
there
> has
> > an article or something that explains how to use it? Perhaps as a
simple
> > console application that has a WSDL2JAVA generated client stub
and just
> adds
> > a usernametoken and calls a service? The test-code that comes
with the
> WSS4J
> > package doesn't seem to use WSDL2JAVA at all, but has the SOAP
XML request
> > built up manually as a string.
> >
> > Thanks for any help,
> > Johan Danforth
>
> --
> Davanum Srinivas - http://webservices.apache.org/~dims/
>
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
