VAST Web service call with header info in SOAP request

[mmahesh_k]

I have deployed a wsdl to connect to internal web server and got the
service object. See below the wsdl...

<wsdl:operation name="MinimalStabilityTest">
<soapbind:operation soapAction="MinimalStabilityTest" style="document"/>
<wsdl:input>
<soapbind:body parts="MinimalStabilityTestRequest" use="literal"/>
<soapbind:header message="rutschblockinterface:MinimalStabilityTestRequestMessage" part="RequestHeader" use="literal"/>
</wsdl:input>

The method 'MinimalStabilityTest' accepts one
parameter as input with one header, that means outgoing SOAP request
will have one header info in the header section and one parameter in the
body section. When i deployed this wsdl, smalltalk
recognized the header as parameter and created method
(MinimalStabilityTest: with:) with two parameters. This way the outgoing
SOAP request will have header info in the body section but as per wsdl the outgoing SOAP request should have one header info
in the header section and one parameter in the body section.

Now my question is why smalltalk web service framework takes the header
message as parameter and create method with additional input for header?

Also how do i pass header info in the SOAP request? Someone please help me in this regard.

Thanks,
Mahesh

[mmahesh_k]

When i invoked method MinimalStabilityTest: with: i got the below error message..

'The type an AbtXmlQName(requestheader:RequestHeader) for WSDL part ''RequestHeader'' could not be determined'.

I debugged the code and found the typeObject of servicepart is nil, the method typeObjectForPart: check for the typeObject, if the typeObject is nil the above error will be popped up. Can someone help me to know what i should do when i have a header info to be passed in the SOAP request?

Thanks,
Mahesh

[tc]

Hello,

The WSDL you posted confuses me a little bit, however, does the service work? For example, the site:

http://www.soapclient.com/soaptest.html

. . . will let you run the service and you can look at the wsdl and soap message source.

--tc

[mmahesh_k]

Yes it is a valid service.

I think am missing something in the code for complex type, the schema for the RequestHeader has three attributes in it.. so i guess i need to do xmlmapping for complex type, but i dont how to do it.. If you have any idea please throw some lights on it..

Thanks,
Mahesh

[tc]

Hello,

Here is a simple example from the XML in a nutshell book:

Code: Select all

<xs:element name="letter">
  <xs:complexType mixed="true">
    <xs:sequence>
      <xs:element name="greeting"/>
      <xs:element name="body"/>
      <xs:element name="closing"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>

The xs:sequence element says those elements have to appear in that order. One can replace xs:sequence with xs:choice meaning one has to appear and xs:all meaning they all have to appear but in any order.

[mmahesh_k]

What shud i do when i get the error message 'The type an AbtXmlQName(requestheader:RequestHeader) for WSDL part ''RequestHeader'' could not be determined'. I got the above error message when creating the payload elements for the SOAP header..
The header info (RequestHeader) is of complex type, anyone please let me know how to pass complex type in the method which will be converted to header elements?

[tc]

Hello,

It may be you are using implicit soap headers which are newer, can you regenerate the wsdl specifying explicit headers and test that?

Thanks.

--tc

[mmahesh_k]

I am using explicit header, header information is part of the portType.
Can you please tell me why the type object is nil for the header?

[tc]

Hello,

The information is not enough for me to pinpoint the exact issue, however, explicit headers are soap v1.2. The insurance example talks about having to include some explicit xml lines for that. Without those lines, the soap processing is done using soap v1.1.

-tc