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=8790>. 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=8790 WSDL2Java produces wrong code for overidden methods, should fail. [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Summary|WSDL2Java produces wrong |WSDL2Java produces wrong |code for overidden methods |code for overidden methods, | |should fail. ------- Additional Comments From [EMAIL PROTECTED] 2002-05-03 19:08 ------- You must name your message stanzas in the portType so the binding can use those same names to map to the appropriate operation (see test/wsdl/clash/clash.wsdl for an example of overloaded operations that work). For example: <wsdl:operation name="getInventory" parameterOrder="authToken chainId hotelId startDate endDate"> <wsdl:input name="in1" message="intf:getInventoryRequest"/> <wsdl:output name="out1" message="intf:getInventoryResponse"/> <wsdl:fault name="fault1" message="intf:SrmsException" name="SrmsException"/> </wsdl:operation> <wsdl:operation name="getInventory" parameterOrder="hotel startDate endDate"> <wsdl:input name="in2" message="intf:getInventoryRequest1"/> <wsdl:output name="out2" message="intf:getInventoryResponse1"/> </wsdl:operation> I'm leaving this bug open, but I changed the summary slightly. WSDL2Java shouldn't have generated code. It should have failed because the binding is not able to match binding operations to portType operations.
