#34657 [Opn]: If you get a communication problem when loading the WSDL, it fatal's
| From: | gareth at wsys dot co dot uk | Date: | Mon, 11 Sep 2006 07:50:34 +0000 |
| Subject: | #34657 [Opn]: If you get a communication problem when loading the WSDL, it fatal's | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-101981@lists.php.net to get a copy of this message | ||
ID: 34657
User updated by: gareth at wsys dot co dot uk
Reported By: gareth at wsys dot co dot uk
Status: Open
Bug Type: SOAP related
Operating System: Windows, Linux
PHP Version: 5.1.6
Assigned To: dmitry
New Comment:
I have tried to use set_error_handler(), but as you know it cannot
catch fatal errors.
Does anyone else have a workaround?
Previous Comments:
------------------------------------------------------------------------
[2006-09-08 21:50:38] tony2001@php.net
See also bug #38703.
------------------------------------------------------------------------
[2006-09-06 10:40:10] gareth at wsys dot co dot uk
Have tried on PHP version 5.1.6, still getting the following error:
Fatal error: SOAP-ERROR: Parsing WSDL: Couldn't load from
'http://urlhere.com/file.wsdl'.
So I still cannot catch this error, which limits my use of SOAP as it
will kill my script.
------------------------------------------------------------------------
[2006-09-05 12:32:44] dmitry@php.net
Seems this bug was already fixed in CVS HEAD, PHP_5_2 and PHP_5_1 long
time ago.
------------------------------------------------------------------------
[2006-01-14 12:08:16] sniper@php.net
Assigned to the maintainer.
------------------------------------------------------------------------
[2006-01-13 14:20:13] gareth at wsys dot co dot uk
The only solution I have come up with for this problem is to put the
SOAP call into a seperate php file and then use it with exec().
This does however limit the input/output options available.
------------------------------------------------------------------------
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
http://bugs.php.net/34657
--
Edit this bug report at http://bugs.php.net/?id=34657&edit=1