Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
1.2
-
None
-
None
Description
Properties of superclass(es) will not be populated in a auto-generated wsdl file.
(The nightly build at 05-Jun-2007 01:27 doesn't fix it).
E.g: the following auto-generated wsdl-fragment of class C2 (extends C1) with the String properties C1.test1 and C2.test2 (see sample code below the wsdl-snippets) will be generated to (and C1 is nowhere else referenced/defined...):
...
<xs:element name="C2" type="ns:C2"/>
<xs:complexType name="C2">
<xs:complexContent>
<xs:extension base="ns0:C1">
<xs:sequence>
<xs:element name="test2" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
...
The Axis2-1.1 version in opposite will create the following (as expected):
...
<xs:element name="C2" type="ns:C2"/>
<xs:complexType name="C2">
<xs:sequence>
<xs:element name="test1" nillable="true" type="xs:string"/>
<xs:element name="test2" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
...
Sample classes C1 and C2:
public class C1 {
private String test1;
public String getTest1()
public void setTest1(String test1)
{ this.test1 = test1; }} // C1
public class C2 extends C1 {
private String test2;
public String getTest2()
public void setTest2(String test2)
{ this.test2 = test2; }} // C2
Attachments
Issue Links
- relates to
-
AXIS2-2744 Testing RPCMessageReceiver with complex data using ADB generated test case
- Resolved