Hi,
it's me again..
I have a complex return type with another complex type inside from my
Axis Java webservice.
In SoapDeserializer the parser comes to this inside complex type. The
order of its members is not than SoapDeSerializer expects.
My intern complex type (all members are inherited by super classes):
type
{
int id;
String name;
String description;
}
The soap response looks as follows:
<type xsi:type="ns1:IEZObjectType">
<description xsi:type="soapenc:string">Beschreibung zu
Objekttyp1</description>
<id xsi:type="xsd:int">1</id>
<name xsi:type="soapenc:string">Objekttyp1</name>
</type>
The client stub tries to deserialize the id first, then the description
and at last the name. When it want to deserialize the id, the parser is
at the the description element and the process fails.
What decide on the order of values?
Falk.
