Another strange behavior in Axis 1.3 final.
 
I have these types:
 
   <xsd:complexType name="Asset" 
                    elementFormDefault="qualified" 
                    targetNamespace="http://myown.ws"; 
                    xmlns=" http://www.w3.org/2001/XMLSchema";>
    <xsd:sequence>
    </xsd:sequence>
   </xsd:complexType>
 
 
   <xsd:complexType name="PaidAsset"  
                    elementFormDefault="qualified" 
                    targetNamespace=http://myown.ws 
                    xmlns=" http://www.w3.org/2001/XMLSchema";>
     <xsd:complexContent mixed="false">
       <xsd:extension base="impl:Asset">
         <xsd:sequence> 
           <xsd:element name="name" nillable="true" minOccurs="0" 
type="xsd:string"/>
         </xsd:sequence>
       </xsd:extension>
     </xsd:complexContent> 
   </xsd:complexType>
 
 
In other words I have a type Asset and a type PaidAsset that is of type Asset.
 
Then I have this type defined:
 
   <xsd:complexType name="ArrayOfAssets"
                    elementFormDefault="qualified" 
                    targetNamespace=" http://arrays.ws " 
                    xmlns="http://www.w3.org/2001/XMLSchema";>
       <xsd:sequence>
         <xsd:element name="item" minOccurs="0" maxOccurs="unbounded" 
type="<namespace>:Asset"/> 
       </xsd:sequence>
   </xsd:complexType>
 
And a method that return an Array of Assets
 
In Axis 1.2.1 this stuff works fine, and Axis 1.3 final though the serializer 
looks like is getting really confused.
 
An item in 1.2.1 on the wire looks like this:
 <item xsi:type="ns1 :PaidAsset" xmlns:ns1= http://myown.ws /> 
 
An item in 1.3 on the wire looks like this:
<item/>
 
What exactly changed in 1.3 that this doesn't work anymore?.
Is this a bug?. Do i do something wrong?
 
I tried this using XMLBeanSerializerFactory too and I have the same behavior
 
Alin

Reply via email to