RE: Bug - Axis uses soapenc:arrayType in wrapped/literal

[Christer Holmér <Ch...@corustechnologies.com>]

I can see that your SOAP response doesn't include any xsi:type declarations.
Try to turn it on in your wsdd.

/Christer

-----Original Message-----
From: Agarwal, Naresh [mailto:nagarwal@informatica.com]
Sent: den 30 september 2003 07:46
To: axis-user@ws.apache.org
Cc: Christer Holmér
Subject: RE: Bug - Axis uses soapenc:arrayType in wrapped/literal


Hi Christer
The soap response I'm getting from axis is as follows. It contains the array
size explicitly in the soap response:
</soapenv:Envelope>
<soapenv:Body>
    <returnarrResponse xmlns="http://DefaultNamespace">
            <returnarrReturn>
                    <a>6</a>
                            <myArr soapenc:arrayType="xsd:int[3]"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
<item xmlns="">1</item>
<item xmlns="">2</item>
<item xmlns="">3</item>
                    </myArr>
            </returnarrReturn>
    </returnarrResponse>
</soapenv:Body>
</soapenv:Envelope>
thanks,
Naresh


-----Original Message-----
From: Christer Holmér [mailto:Christer.Holmer@corustechnologies.com]
Sent: Monday, September 29, 2003 2:38 PM
To: axis-user@ws.apache.org
Subject: RE: Bug - Axis uses soapenc:arrayType in wrapped/literal


This might not be of very much help, but hopefully bring some hope. I have
been experiencing problems with soap arrays and .NET, but it works for us
now. I don't remember the details, but I think we had to specify the array
size explicitly in the actual soap message.

<ArrayOfTransaction xsi:type="soapenc:Array"
soapenc:arrayType="ns2:Transaction[1]">
  <item href="#id2" /> 
</ArrayOfTransaction>


I hope this helps in some way!

Regards,
Christer
-----Original Message-----
From: Agarwal, Naresh [mailto:nagarwal@informatica.com]
Sent: den 26 september 2003 11:39
To: Axis (E-mail)
Subject: Bug - Axis uses soapenc:arrayType in wrapped/literal


Hi

Axis uses *soapenc:arrayType*  for encoding the *arrays* in wrapped/literal
type of services.. 

Due to this fact, axis services, which returns array _CAN_NOT_ be consumed by
.Net clients.

Is anyone looking into this issue. Are there any workarounds? Any help will
be greatly appreciated!

thanks,
Naresh