I get the same results in Axis 1.2RC3. David
David Robison wrote:
I am using Axis 1.1
David
David Robison wrote:
I get the same result when I use the following type in my wsdl:
<types>
<xsd:schema>
<xsd:complexType name="segment_typeArray">
<xsd:sequence>
<xsd:element name="segmentType"
type="crisVocab:segment_typeTYPE" minOccurs="0" maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</types>
David
David Robison wrote:
One other possible point of interest is that the actual data in the
segment_typeTYPE is contained in attributes. I don't know if this is
important or not...
David
David Robison wrote:
I have a soap service that is trying to return an array of objects
back to the client. The WSDL definition is:
<types>
<xsd:schema>
<xsd:complexType name="segment_typeTYPEArray">
<xsd:complexContent>
<xsd:restriction base="soapenc:Array">
<xsd:attribute ref="soapenc:arrayType"
wsdl:arrayType="crisVocab:segment_typeTYPE[]"/>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
</xsd:schema>
</types>
The SOAP service prepares a java array of segment_typeTYPE objects
and returns the array. On the server side the different element in
the array all contain different data. However, when I examine the
returned SOAP message, I see the correct number of elements
returned, but they all have the same data! The type mapping in the
WSDD is:
<typeMapping
xmlns:ns="urn:MIMOSAReg"
qname="ns:segment_typeTYPEArray"
type="java:org.mimosa.www.TechXMLV3_0.Segment_typeTYPE[]"
serializer="org.apache.axis.encoding.ser.ArraySerializerFactory"
deserializer="org.apache.axis.encoding.ser.ArrayDeserializerFactory"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
/>
Any thought on what I may be doing wrong?
Any help would be appreciated.
David Robison
--
David R Robison
Open Roads Consulting, Inc.
708 S. Battlefield Blvd., Chesapeake, VA 23322
phone: (757) 546-3401
e-mail: [EMAIL PROTECTED]
web: http://openroadsconsulting.com
blog: http://therobe.blogspot.com