[SOAP] PHP5 error "looks like we got no XML document"
| From: | Colin Goldberg | Date: | Fri, 15 Sep 2006 01:05:36 +0000 |
| Subject: | [SOAP] PHP5 error "looks like we got no XML document" | ||
| References: | 1 2 3 | Groups: | php.soap |
| Request: | Send a blank email to php-soap+get-2370@lists.php.net to get a copy of this message | ||
Hi All,
I am getting this error ("looks like we got no XML document") that is strangely bare (no SoapFault packet). I am currently using php5.1.2. Am I to understand that this will disappear with a php upgrade?
I have also seen references to trailing spaces after the ?> at the end of the file having something to do with this. Can anyone enlighten me?
Thanks
Colin Goldberg
MacMicro Inc - Web Applications & Services <http://www.MacMicro.com>
BizConnector - for Contextual Interaction <http://www.BizConnector.com>
mslemko wrote:
Thanks, I came to the same conclusion shortly after writing this note and submitted as a bug (Bug #36854) on bugs.php.net. I got a response from there to use the latest CVS build of php 5.1 (5.1.3RC2) and it was fixed. -Mark Dmitry Stogov wrote:This is probably a bug. Please open bug report on http://bugs.php.net/ with small reproduce case. You can assign it to "dmitry" to get fix faster. Thanks. Dmitry.-----Original Message----- From: mslemko [mailto:mslemko@netscape.net] Sent: Saturday, March 25, 2006 2:56 AM To: soap@lists.php.net Subject: [SOAP] has anyone use a SoapClient within a SoapServer implementation inphp5? Hi, I'm wondering if anyone has had this same problem and found a workaround? I am trying to use a SOAP client within a SOAP server and it caused the SOAP server to fail to respond properly to its clients with a SoapFault when a problem arose. It works fine if there is no error to return to the client. so a diagram might help... [SOAP Client A]| |[SOAP Server A] +[SOAP Client B] ---> [SOAP Server B] +[return SoapFault] ...looks like we got no XML document... The response (SoapFault) to the SOAP Client A looks like it is empty. I'm wondering if the SoapFault mechanism is corrupted by the SoapClient initialization. I've tested the idea of faking a response from the SOAP Server B, i.e. don't create a SOAP Client B, and the returning SoapFault works as expected. tested on these: PHP 5.1.2 IIS 6 PHP 5.1.1 Apache 2 -- PHP Soap Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php