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=17546>. 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=17546 WSDL problem with restricted types Summary: WSDL problem with restricted types Product: Axis Version: 1.1RC1 Platform: PC OS/Version: Windows XP Status: NEW Severity: Major Priority: Other Component: WSDL processing AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The attached WSDL file contains a type definition with a restriction (non- negative integer): <xsd:element name="value"> <xsd:simpleType> <xsd:restriction base="xsd:int"> <xsd:minInclusive value = "0"/> </xsd:restriction> </xsd:simpleType> </xsd:element> When the request is made using the generated proxies (WSDL2Java), then the argument (e.g. 4711) is included in the SOAP body without any type specification. Should not at least the base type xsd:int appear in the payload? Excerpt from the payload (encoding of the value argument): <multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; xsi:type="ns2:id" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:ns2="http://www.gruntz.ch/schemas/aaa";> <value href="#id1"/> </multiRef> <multiRef id="id1" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";> 4711 </multiRef> If I remove the definition of the restriction in the WSDL file the type is added, therefore I conclude that it is a WSDL processing bug. - Dominik
