Bug #47584 [Com]: WSDL error in soapClient causes Fatal Error

Edit report at https://bugs.php.net/bug.php?id=47584&edit=1 ID: 47584 Comment by: zpon dot dk at gmail dot com Reported by: gem at rellim dot com Summary: WSDL error in soapClient causes Fatal Error Status: Bogus Type: Bug Package: SOAP related Operating System: Linux PHP Version: 5.2.9 Assigned To: dmitry Block user comment: N Private report: N New Comment: I had to surround my SoapClient call with xdebug_disable(); and xdebug_enable(); (@ was not enough) to work around this problem. Previous Comments: ------------------------------------------------------------------------ [2010-09-02 21:10:09] gem at rellim dot com I was a confirmed bug in earlier versions. So it should be 'Fixed' not "Bogus'. ------------------------------------------------------------------------ [2010-09-02 19:37:13] rasmus@php.net Right, so this is not a PHP bug. Perhaps a feature request to downgrade that particular error to a Warning instead of a catchable fatal, but that is all I see. ------------------------------------------------------------------------ [2010-09-02 19:34:19] gem at rellim dot com I do see it catchable now without XDebug. # php tmp.php SOAP-ERROR: Parsing WSDL: Couldn't load from 'non-existent.wsdl' : failed to load external entity "non-existent.wsdl" ok # ------------------------------------------------------------------------ [2010-09-02 19:33:05] gem at rellim dot com Not catchable for me with XDebug and your example: # cat tmp.php <?php try { $x = @new SoapClient("non-existent.wsdl",array("exceptions" => 1)); } catch (SoapFault $E) { echo $E->faultstring; } echo "ok\n"; ?> # php tmp.php # ------------------------------------------------------------------------ [2010-09-02 19:22:02] rasmus@php.net It is a catchable fatal though. eg. <?php try { $x = @new SoapClient("non-existent.wsdl",array("exceptions" => 1)); } catch (SoapFault $E) { echo $E->faultstring; } echo "ok\n"; ------------------------------------------------------------------------ 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 https://bugs.php.net/bug.php?id=47584 -- Edit this bug report at https://bugs.php.net/bug.php?id=47584&edit=1