[jira] Resolved: (AXIS-1334) ArraySerializer incompatible using DII with doc/lit services (i.e. .NET)

["Davanum Srinivas (JIRA)" <ax...@ws.apache.org>]

     [ http://issues.apache.org/jira/browse/AXIS-1334?page=all ]
     
Davanum Srinivas resolved AXIS-1334:
------------------------------------

    Resolution: Fixed

I believe this has been fixed in Axis 1.2.1. If it isn't, add a comment and i'll reopen the bug.

thanks,
dims

> ArraySerializer incompatible using DII with doc/lit services (i.e. .NET)
> ------------------------------------------------------------------------
>
>          Key: AXIS-1334
>          URL: http://issues.apache.org/jira/browse/AXIS-1334
>      Project: Apache Axis
>         Type: Bug
>     Versions: 1.2 Beta
>  Environment: Windows 2003, JDK 1.4.2_03, Xerces, Axis 1.2 beta, .NET framework 1.1
>     Reporter: Rich Magnuson

>
> I'm using DII to invoke a doc/lit web service hosted by .NET.  A web method's input parameter is an array of a simple type, say string.  The WSDL describing the input is:
> <s:complexType name="ArrayOfString">
>   <s:sequence>
>     <s:element minOccurs="0" maxOccurs="unbounded" name="string" nillable="true" type="s:string" /> 
>   </s:sequence>
> </s:complexType>
> So the server expect the array elements to be named <string> as per the 'name' attribute, but Axis serializes all array elements with <item>, so the SOAP request sent contains
> <inArr soapenc:arrayType="ns1:ArrayOfString[3]" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
>     <item xsi:type="xsd:string" xmlns="">string1</item>
>     <item xsi:type="xsd:string" xmlns="">string2</item>
> This is rejected by .NET, which wants the array elements to be named <string> and the array object to use literal encoding.
> My code is modeled from the DynamicInvoker class in Axis samples (thanks, Dims!).  This is not a problem using server-side stubs.
> I notice some hardcodes in ArraySerializer and VectorSerializer to always use Constants.QNAME_LITERAL_ITEM ("<item>").  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira