Forum OpenACS Q&A: tSOAP arrays

Collapse
1: tSOAP arrays
Posted by brian hennessey on 04/11/05 09:32 PM 
When I use the tSOAP package to create a client side
message, each array element in a complex type is 
designated with an "item" element.
(this seems to be standard)

For Example:
<complexType>
 <item>
  <element1>data1</element1>
  <element2>data2</element2>
 </item>
 <item>
  <element1>data4</element1>
  <element2>data5</element2>
 </item>
</complexType>


It appears the .Net server is expecting each element to be
named instead of the element "item". Such as:
<complexType>
  <arrayName>
    <element1>data1</element1>
    <element2>data2</element2>
  </arrayName>


Is this correct, or am I missreading the sample request. 
Is there a way to use the element names instead of "item"?

Thanks for any help.

--brian
Collapse
2: Re: tSOAP arrays (response to 1)
Posted by brian hennessey on 04/13/05 06:15 PM 
More information...

tSOAP is using SOAP encoding 1.1 whereas the .Net server is using "no encoding". There appears to be no option to turn encoding off/set to none. 

SOAP-procs.tcl:

360     # Default SOAP encoding is SOAP 1.1
361     if { $procvar(encoding) == {} } {
362         set procvar(encoding) SOAP1.1
363     }
364     switch -glob -- $procvar(encoding) {
365         SOAP1.1 - 1.1 {
366             set procvar(encoding) "http://schemas.xmlsoap.org/soap/encoding/"
367         }
368         SOAP1.2 - 1.2 {
369             set procvar(encoding) "http://www.w3.org/2001/soap-encoding"+
370         }
371     }
372

Has anyone gotten around this?

Thanks for any help.
Collapse
3: Re: tSOAP arrays (response to 1)
Posted by Jade Rubick on 05/15/07 08:07 PM
Did you have any luck with this, Brian?