I wrote a test and a fix for this bug a few days ago. Both patches are
included in the ticket. I do realize that Dmitry, the one assigned the bug
might be busy and that the patch might take a while to get reviewed.
However, I want to make sure that there is no administrative step on my part
holding things up. Is there any action I have failed to take in my attempts
to resolve this ticket, or do I just have to be patient?


---------- Forwarded message ----------
From: PHP Bug Database <php-bugs@lists.php.net>
Date: Fri, 2 Apr 2010 20:51:16 +0200 (CEST)
Subject: Req #50698 [Opn->Asn]: SoapClient should handle wsdls with
some incompatiable endpoints
To: zippy1981@gmail.com

ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at

ID: 50698
Updated by: felipe@php.net
Reported by: zippy1981 at gmail dot com
Summary: SoapClient should handle wsdls with some incompatiable
-Status: Open
+Status: Assigned
Type: Feature/Change Request
Package: *General Issues
Operating System: Windows XP/7 and probably all.
PHP Version: 5.2.12, 5.3.1
-Assigned To:
+Assigned To: dmitry

Previous Comments:
[2010-04-02 20:48:18] zippy1981 at gmail dot com

Submitted a new patch with error handling.

[2010-04-02 17:29:49] zippy1981 at gmail dot com

Below is a patch that helps to fix the behavior. The following problems

1) If the wsdl contains only non http endpoints, and the location
parameter is
not specified, a proper error message is not generated.
2) If the wsdl contains only non http endpoints, and the location
parameter is
specified, the error "Uncaught SoapFault exception: [Client] Function
is not a valid method for this service in File.php:21" is displayed.

Index: ext/soap/php_sdl.c
--- ext/soap/php_sdl.c (revision 297339)
+++ ext/soap/php_sdl.c (working copy)
@@ -832,7 +832,12 @@
children->content, WSDL_HTTP_TRANSPORT, sizeof(WSDL_HTTP_TRANSPORT)) ==
0) {
} else {
soap_error1(E_ERROR, "Parsing WSDL: PHP-SOAP doesn't support transport
+ // Since
this is
an E_NOTICE severity message, it will disappear into the ether.
soap_error1(E_NOTICE, "Parsing WSDL: PHP-SOAP doesn't support transport
+ trav = trav-
+ continue;

[2010-01-13 20:59:45] zippy1981 at gmail dot com

Thanks for your reply.

On my initial report I posted an example client. In a comment in the
example client is a link to a github repo with a .NET web service that
causes this issue (e.g. config file was bound to nettcp):


Inside the .net service is also a copy of the PHP client.

The .NET code can be compiled on any windows machine with the free IDE
SharpDevelop (http://www.icsharpcode.net/OpenSource/SD/Download/)

I can provide a manually generated wsdl with false endpoints if needed.

I'll gladly help test a fix or provide a mock if needed.

[2010-01-13 20:29:39] srinatar@php.net

thanks for the clarification. if you can provide a test case /script ,
it would help us to work on this. thanks again for taking time for
following up on this. your help will definitely help PHP make better !

[2010-01-13 15:05:54] zippy1981 at gmail dot com

It seems I was not clear in my original ticket.

My soap service has two end points. One is http (soap 1.1). The other
is nettcp, microsoft private protocol.

PHP throws an error when I parse the WSDL simply because it contains
an endpoint it can't connect to. This is in spite of the following
four facts:

1) There is a http endpoint it knows how to connect to in the WSDL
2) I override the WSDL endpoints in the soap constructor.
3) A soap client only needs to connect to one endpoint in a WSDL to
communicate with it

If I manually edit the WSDL so that the nettcp endpoint is no longer
advertised, but it still exists, PHP will connect to it fine.


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at


Sent from my mobile device

Sent from my mobile device

Search Discussions

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupphp-internals @
postedApr 9, '10 at 2:03a
activeApr 9, '10 at 2:03a

1 user in discussion

Justin Dearing: 1 post



site design / logo © 2022 Grokbase