ID: 49169 Comment by: bigdan at gmail dot com Reported By: jeroen at asystance dot nl Status: Verified Bug Type: SOAP related Operating System: linux PHP Version: 5.2SVN-2009-08-05 (snap) New Comment:
Nevermind on the workaround - either this is not a bug, this issue was noticed well before this bug, or the comments here are entirely unrelated though they correct the issue for me: http://us3.php.net/manual/en/soapserver.handle.php#81750 TLDR: Instead of <soap:binding style="document you need to use <soap:binding style="rpc Previous Comments: ------------------------------------------------------------------------ [2009-09-18 13:45:30] bigdan at gmail dot com? Is anyone aware of a workaround? I am having this issue on Ubuntu Hardy. Thanks ------------------------------------------------------------------------ [2009-09-09 19:27:50] sjo...@php.net Could reproduce. Even though the soap action looked as follows: SOAPAction: "operation2" Operation 1 was called. ------------------------------------------------------------------------ [2009-08-20 15:18:33] robin dot harvey at chaptereight dot com Hi, This bug is affecting me too, and I've noticed that it's only the input parameters which trigger the bug - 2 functions can have the same output and they are treated individually. Also, it seems that it's the order of the wsdl:binding/wsdl:operation declarations which makes a difference, swapping the wsdl:portType/wsdl:operation or wsdl:message ordering does not trigger the bug. HTH --Robin ------------------------------------------------------------------------ [2009-08-05 11:13:06] jeroen at asystance dot nl The correct link to the test case is http://jayvee.nl/soaptest2.tar (without the comma) ------------------------------------------------------------------------ [2009-08-05 11:11:00] jeroen at asystance dot nl Description: ------------ When two <wsdl:operation>s have the same API (that is, have the same <wsdl:message>s), the SoapServer calls the function corresponding to the _first_ <wsdl:operation> specified in the <wsdl:binding>, even although the SoapClient sends the correct "SOAP action" header, which is correctly received on the server. Reproduce code: --------------- Download http://jayvee.nl/soaptest2.tar, untar and change the URL in interface.wsdl call SAOPTest.php, which is both a client and server. The server will produce a log that the client outputs, so you can see what the server is doing. Expected result: ---------------- Independent of the order in which the <wsdl:operation>s are listed in the <wsdl:binding> element, the SoapServer should call the function corresponding to the "SOAP action" header specified in the request. Actual result: -------------- The SoapServer always calls the function corresponding to the _first_ <wsdl:operation> specified. In the test case, the server will call "function operation1()" twice, even though the second call is to operation2, and the "SOAP action" header's value is "operation2" To verify, switch the <wsdl:operation> elements in the <wsdl:binding> element and run SOAPTest.php. You will see that the server will call "function operation2()" twice, even though the "SOAP action" headers are different. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=49169&edit=1
