You don't necessarily have to write code to inject the headers, although
that's usually the most straightforward solution.
WAS can attach policy sets to web service consumers and providers that
can handle most WS-Security functions, including a plain user id/password
header.
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Neill Harper
Sent: Friday, April 09, 2010 7:14 PM
To: 'Web Enabling the AS400 / iSeries'
Subject: Re: [WEB400] Web Services (again!)
Can we see the WSDL please?
I find a lot of the java and c++ tools that generate stubs from a wsdl, do
not support soap headers in a friendly manner.
You have to write user functions that hook into the request response life
cycle that inject into or retrieve from the message the soap headers as
required.
This is one area where the .NET tools to prove more useful.
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Jon Paris
Sent: 09 April 2010 18:20
To: web400@xxxxxxxxxxxx
Subject: Re: [WEB400] Web Services (again!)
That was what I expected - but the Soap headers generated from the
wsdl have no such entry.
I'm hoping that someone on the java or midrange lists have experienced
this so I've posted over there. As I told Aaron I have a work around
(PW = UserId) but it is not goodness.
Jon Paris
www.Partner400.com
www.SystemiDeveloper.com
On Apr 9, 2010, at 1:00 PM, web400-request@xxxxxxxxxxxx wrote:
Are you sending the SOAP header? The user/password is normally sent
in
there.
midrange.com
