axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 26548] - local xsd:group constructs are not processed properly
Date Thu, 05 Feb 2004 14:02:38 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26548>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26548

local xsd:group constructs are not processed properly





------- Additional Comments From hplanting@mail.com  2004-02-05 14:02 -------
Sorry - I wasn't aware of that. 

Here is some information about what the fix does:

The xs:group construct allows for a list of xs:elements to be defined as
belonging to a group. With this change a TypeEntry is created for each
referenced global Group construct. After code generation, a separate class will
be generated for each refered global group. Each local group definition with a
'ref' attribute will result in a reference being created to the global group.

Suppose a WSDL document contains the following schema definitions:

...
<xs:group name="myGroup">
  <xs:sequence>
    <xs:element name="areaCode" type="xsd:int"/>
    <xs:element name="exchange" type="xsd:string"/>
  </xs:sequence>
</xs:group>

<xs:complexType name="phone">
  <xs:group ref="typens:myGroup"/>
</xs:complexType>
...


The classes representing the group 'myGroup' and complexType 'phone' will
be generated as follows:

public class MyGroup  implements java.io.Serializable {
    private int areaCode;
    private java.lang.String exchange;
    private java.lang.String number;
...
}

public class Phone  implements java.io.Serializable {
    private AddressFetcher.MyGroup myGroup;
...
}

Mime
View raw message