Edit report at https://bugs.php.net/bug.php?id=50547&edit=1
ID: 50547
Comment by: akg_67 at hotmail dot com
Reported by: rsumibcay at reddoor dot biz
Summary: SoapServer Fatal errror in WSDL mode
Status: Open
Type: Bug
Package: SOAP related
Operating System: Ubuntu Linux
PHP Version: 5.2.12
Block user comment: N
Private report: N
New Comment:
I experience this issue today. I am using PHP 5.4.4/MAMP on a MBP and also
experienced same issue on my GoDaddy shared hosting service.
soapUI indicated line 817: Invalid double value in XML Response. Basically, one
of the parameter on Line 817 has value "" instead of double as expected.
I haven't been able to figure out how to overcome this issue in PHP SOAPClient
soapCall. I just have to wait until the incorrect value line is no longer in
the
XML response.
Exception: SOAP-ERROR: Encoding: Violation of encoding rules
*** Last Request Headers ***
string(249) "POST /ws/1.3 HTTP/1.0
Host: www.lendingclub.com
Connection: close
User-Agent: PHP-SOAP/5.4.4
Content-Type: text/xml; charset=utf-8
SOAPAction: "LoanBrowseLoans"
Content-Length: 230
Authorization: Basic <redacted authorization string>
"
*** Last Request ***
string(230) "
"
*** Last Response Headers ***
string(255) "HTTP/1.0 200 OK
Content-Type: text/xml;charset=utf-8
Date: Wed, 05 Jun 2013 22:04:28 GMT
Server: ECS (sea/1C0B)
Set-Cookie: www.lendingclub.com-ws_grp=IDDCKIMA; Expires=Thu, 06-Jun-2013
22:01:20 GMT; Path=/
Content-Length: 367010
Connection: close
"
*** Last Response ***
string(367010) "2013-06-05T15:04:28.391-07:00"
Can not process further due to error
Previous Comments:
------------------------------------------------------------------------
[2012-06-11 11:22:12] agastiya at gmail dot com
I also experience this when running on PHP 5.2+ and 5.3+. My script run
flawlessly
on PHP 5.1.6. so maybe the encoding rules were not applied strictly on version
5.1
than on the newer version?
I vote for adding option to let the call pass through so that more validation
can
be handled manually at PHP level.
------------------------------------------------------------------------
[2012-02-09 14:15:54] dp0 at yandex dot ru
Encoding: Violation of encoding rules
was my problem too, when trying to work with WSDL created in JAVA.
The problem was solved by moving to using the 1.2 version of SOAP on server and
client.
------------------------------------------------------------------------
[2011-08-17 14:28:34] chinigo at gmail dot com
mdekrijger's suggestion about disabling Xdebug worked for me too. Adding
xdebug_disable() immediately before the SOAP call resulted in a Fatal SOAP
error
being converted to a catchable SOAP fault.
------------------------------------------------------------------------
[2011-02-24 16:00:36] mdekrijger at e-sites dot nl
Xdebug might be the problem. When using xdebug_disable() before calling the
handle() method, the server responds with a proper SOAP message which says that
something went wrong.
------------------------------------------------------------------------
[2011-02-24 09:54:31] mdekrijger at e-sites dot nl
Does anyone have an alternative solution for this problem? (while this bug
remains
open?)
We really want to provide some information about the wrong type in the return
soap
response. So implementing our SOAP services would be a much easier job.
------------------------------------------------------------------------
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=50547
--
Edit this bug report at https://bugs.php.net/bug.php?id=50547&edit=1
