You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by JabberW <ja...@gmail.com> on 2006/11/08 17:25:22 UTC
strange inheritance handling by Java2WSDL
Hi all.
I'm trying to generate a WSDL for simple service with some extended
data type (see below the example). Axis 1.2.1 I used previously
generates it in pretty reasonable way (max/min occurs are deleted for
sake of clearness):
<complexType name="Data_A">
<sequence>
<element name="val_1" type="xsd:string"/>
</sequence>
</complexType>
<complexType name="Data_B">
<complexContent>
<extension base="tns1:Data_A">
<sequence>
<element name="val_2" type="xsd:string"/>
</sequence>
</extension>
</complexContent>
</complexType>
While Axis2-11 substitutes the extension by simple including:
<xs:complexType name="Data_B">
<xs:sequence>
<xs:element name="val_1" nillable="true" type="xs:string"/>
<xs:element name="val_2" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
Is it correct basically? Is it possible to enforce new Axis to
generate it in the old-fashion way with all type relations restored?
Greatly appreciate any inputs,
Sincerely,
Jabb. (jabberw-at-gmail)
////////////// example /////
class MySvc {
public String myOp(Data_B)
}
where:
public class Data_A {
public void setVal_1(String s){}
public String getVal_1(){}
}
and
public class Data_B extends Data_A {
public void setVal_2(String s){}
public String getVal_2(){}
}
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org