Edit report at http://bugs.php.net/bug.php?id=47584&edit=1
ID: 47584
Comment by: pwb at evanr 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
New Comment:
This is a real issue, even when the SoapClient is set to throw
exceptions and not
errors. This fatal error cannot be defeated even with the exceptions
option set
to true.
We're experiencing this in 5.2.13 on linux x64.
A fatal error is thrown not only when WSDL can't be loaded but as well
when an
internal reference in the WSDL (e.g. to a namespace) cannot be
imported/resolved.
Previous Comments:
------------------------------------------------------------------------
[2009-03-06 17:49:08] gem at rellim dot com
Why does it work OK for you and not for me? Just because it
works on one host for you does not mean it does not fail for me.
This is the entire program to reproduce:
<?php
$client = new soapClient('http://google.com');
?>
PHP Fatal error: SOAP-ERROR: Parsing WSDL: XXXX
I can reproduce on several different hosts. I am not
running Xdebug, eaccelerator, or any other add in.
------------------------------------------------------------------------
[2009-03-06 15:32:18] [email protected]
It already works that way.
------------------------------------------------------------------------
[2009-03-06 07:42:50] gem at rellim dot com
Description:
------------
Basically bug# 34657 says it all, except the bug is not bogus.
I am NOT running Xdebug and any problem reading the remote WSDL
causes a fatal error which makes it impossible to inform the
user nicely of the problem.
Reproduce code:
---------------
$client = new SoapClient('http://google.com');
Expected result:
----------------
I would like to see a catchable error or an error return;
Actual result:
--------------
PHP Fatal error: SOAP-ERROR: Parsing WSDL: Couldn't load from
'http://google.com'
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/bug.php?id=47584&edit=1
