I have a schema, that I do not control, that has the following structures:
<xsd:element name="GriddedData">
<xsd:annotation>
<xsd:documentation>
Definition:
A request for METOC grid data.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:choice>
<xsd:element
ref="GriddedAnalysisForecast"/>
<xsd:element ref="GriddedClimatology"/>
</xsd:choice>
<xsd:element ref="ConstraintParameters"
minOccurs="0"/>
<xsd:element ref="Location"/>
<xsd:element ref="Time" minOccurs="0"/>
<xsd:element ref="Process" minOccurs="0"/>
<xsd:element ref="GridParameter"
maxOccurs="unbounded"/>
<xsd:element ref="ReProjection" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
The elements in bold, GriddedAnalysisForecast and GriddedClimatology, are
required, but are mere placeholders for future development and are defined
as follows:
<xsd:element name="GriddedClimatology"/>
<xsd:element name="GriddedAnalysisForecast"/>
Whenever I run wsdl2java against this XSD, all class files are generated,
except for these two. I can get the files to create if I go in, change the
XSD to put bogus attributes into the elements, but this is not maintainable,
as I have no control over the XSD.
Is there a switch, or some method that I could use to make sure the
wsdl2java generates ALL elements, including the empty ones?
--
View this message in context:
http://www.nabble.com/wsdl2java-does-not-create-classes-for-empty-elements-tp20858115p20858115.html
Sent from the cxf-user mailing list archive at Nabble.com.
