Johan, to enable an Axis client to use WSS4J features is straight forward: just take your WSDL file and generate all necessary client files with WSDL2JAVA, nothing needs to be done for WSS4J in this step. You may enable the option to have WSDL2JAVA generate the client's Axis deployment file (*.WSDD).
This is the main difference between a "standard" Axis client and a WSS4J enabled client: - a "standard" Axis client usually does not need a deployment file if it's just using standard Axis features, e.g. for serialization, etc. - to enable an Axis client to use WSS4J it is mandatory to have a client deployment file because this deployment file contains all necessary information to setup the WSS4J Axis handlers. Usually the client source code does not need to be modified to use WSS4J together with Axis. In most cases WSS4J is transparent to the client. An example of such a client side deployment file is in the interop directories. Regards, Werner > -----Urspr�ngliche Nachricht----- > Von: Johan Danforth [mailto:[EMAIL PROTECTED] > Gesendet: Freitag, 7. Januar 2005 15:00 > An: 'Werner Dittmann' > Cc: [email protected] > Betreff: RE: tutorials or walkthroughs? > > > Werner, > Yes, I've looked at that file and I've browsed through > most of the > source code that comes with WSS4J without much success I'm > afraid. I could > give it another go I guess, but I don't want to spend days to > get into it. > Can someone just explain the steps in a pseudo-way maybe? > BTW. If there are problems getting WSS4J working with > ASP.NET + WSE > 2.0, maybe I shouldn't go down that route right now anyway... > I need to send > a binary token from java soap (axis) clients to web services > built with > ASP.NET, so maybe I should just use normal soap headers for now. > /Johan > -----Original Message----- > From: Werner Dittmann [mailto:[EMAIL PROTECTED] > Sent: den 7 januari 2005 13:13 > To: Johan Danforth > Cc: [EMAIL PROTECTED]; 'Ted Toth'; [email protected] > Subject: Re: tutorials or walkthroughs? > > Johan, > > sorry for the lack of documentation so far. I'm sure > you already > looked > at the "package.html" file in > "src/org/apache/ws/axis/security". In > addition > you may have a look at the interop examples. > > If you have a complete checkout of wss4j the pls go to > the "specs" > directory. > This dir contains the "ping.wsdl" file that is used to > build the > interop > scenarios > as defined by OASIS. The resulting *.java classes > (from WSDL2JAVA) > are in > "build/work/org/apache/ws/axis/oasis/ping". The other parts are > located in > "interop/org/apache/ws/axis/oasis/*". > > Hope this gets you a step further. > > Regards, > Werner > > Johan Danforth schrieb: > > > 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? > > > ><snip> > > > > > > >
