>
>
>> >> Are you saying that adding a axis2.conf file will enable
>> > the creation of the security header?
>>
>
> In my case I have the same client .java code that can talk
> to WebService both with and without WS-Security.
> The only difference is axis2.conf.
>
>
I'll give this a shot today. W
>
>
> I used Rampard.
> There is good tutorial:
>
> http://www.ibm.com/developerworks/webservices/tutorials/ws-understand-web-services4/
>
> My client .java code look the same with and without WS-Security.
> All the difference is in configuration axis2.conf file.
> You must know what cryptography (
My head asplode. If someone can point me in the right direction here, I'll
be very grateful.
I have a third party wsdl which I've used (wsdl2java) to generate my client
stub and test classes. When I run my test, the SOAP message is being
generated just fine, but the ws-security headers are fore
