On 6/30/06, Magnus Bergman <[EMAIL PROTECTED]
> wrote:
Hi,
I'm trying to consume a .NET webservice. I'm using Axis1.4. The service
is published with the attached wsdl. The service is using soap:headers,
which seems to me not to be very straightforward. If I run wsdl2java
against the published wsdl I will not get a method that accepts the
header-type as an argument, but after scanning this list I found a tip
that said how I could manually edit the original wsdl from:
...
<wsdl:message name="LoginUserSoapIn">
<wsdl:part name="username" type="s:string" />
<wsdl:part name="password" type="s:string" />
</wsdl:message>
...
to:
...
<wsdl:message name="LoginUserSoapIn">
<wsdl:part name="username" type="s:string" />
<wsdl:part name="password" type="s:string" />
<wsdl:part name="authentication"
type="tns:SoapAuthenticationHeader"/>
</wsdl:message>
...
this will get me a method that accepts the Header-type. Fine! But when I
call my newly generated method I see (by using TCPMonitor) no headers in
my request and the server is answering with a http response 500 - Server
did not recognize the value of HTTP Header SOAPAction:
http://gitapi.golf.se/Permission/Permission2/LoginUser?
I'm guessing that "HTTP Header SOAPAction" has nothing to do with the
missing soap:header but I decided to inform you about that anyway.
Does anybody have any suggestion how to get the the soap:header-stuff
working? If I should solve this issue with handlers I would really
appreciate some code snippets.
Thanks,
magnus
--
------------------------------------
Magnus Bergman
www.voiceprovider.se
Mobile +46(0)733 63 42 08
Office +46(0)8 525 080 08
Fax +46(0)8 456 96 61
Slottsbacken 6
111 30 Stockholm
------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
