WsGen incorrectly handles xs:all in WSDL
----------------------------------------
Key: XFIRE-1062
URL: http://jira.codehaus.org/browse/XFIRE-1062
Project: XFire
Issue Type: Bug
Affects Versions: 1.2.6
Reporter: Zachary Jones
Assignee: Dan Diephouse
For a given operation like:
<wsdl:operation name="doIt">
<wsdl:input name="doItRequest" message="tns:doItRequest" />
<wsdl:output name="doItResponse" message="tns:doItResponse" />
</wsdl:operation>
where the wsd:message is defined like:
<wsdl:message name="doItRequest">
<wsdl:part name="parameters" element="tns:doIt" />
</wsdl:message>
If the definition of the doItRequest looks like the following:
<xs:element name="doIt">
<xs:complexType>
<xs:all>
<xs:element name="how" type="xs:string" />
<xs:element name="when" type="xs:string" />
</xs:all>
</xs:complexType>
</xs:element>
WsGen Fails to generate the correct stub. The method called from the generated
endpoint will have no parameters. If the "doIt" element was defined using
xs:sequence, WsGen works correctly:
<xs:element name="doIt">
<xs:complexType>
<xs:sequence>
<xs:element name="how" type="xs:string" />
<xs:element name="when" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
