ext/soap uses php_libxml_switch_context from ext/libxml, however it
doesn't provide internal equivalent for libxml_use_internal_errors().
Thanks. Dmitry.
Hannes Magnusson wrote:
On Fri, Aug 29, 2008 at 17:08, Dmitry Stogov [EMAIL PROTECTED] wrote:
Especially for this situation warnings are
On 01.09.2008, at 11:29, Dmitry Stogov wrote:
ext/soap uses php_libxml_switch_context from ext/libxml, however it
doesn't provide internal equivalent for libxml_use_internal_errors().
Thanks. Dmitry.
Hannes Magnusson wrote:
On Fri, Aug 29, 2008 at 17:08, Dmitry Stogov [EMAIL PROTECTED]
On Mon, Sep 1, 2008 at 16:57, Dmitry Stogov [EMAIL PROTECTED] wrote:
After some thoughts I decided to disable warnings.
The fix is committed into HEAD and PHP_5_3.
Is that something that should be documented anywhere? NEWS? manual?
wiki? blog? twitter?
-Hannes
p.s.
Please stop top-posting. It
On 13.08.2008, at 14:31, David Zülke wrote:
True, it indeed does since 5.3... but what about that warning; does
it have to be raised at all? if the exceptions option is passed?
Am 08.08.2008 um 09:39 schrieb Dmitry Stogov:
Hi,
I took a quick look into the issue and I didn't found a
Am 29.08.2008 um 13:11 schrieb Lukas Kahwe Smith:
On 13.08.2008, at 14:31, David Zülke wrote:
Am 08.08.2008 um 09:39 schrieb Dmitry Stogov:
Hi,
I took a quick look into the issue and I didn't found a problem.
SoapClient constructor already throws exceptions in case of WSDL
errors.
?php
On Fri, Aug 29, 2008 at 17:08, Dmitry Stogov [EMAIL PROTECTED] wrote:
Especially for this situation warnings are generated by libxml.
I don't like to disable these warnings in ext/soap, because in some
situation libxml may generate warnings and then return parsed document.
So SoapClient()
On 27.07.2008, at 15:07, Knut Urdalen wrote:
Hi David,
That would be great! Currently I need to call the WSDL-file two
times to be able to handle the exception.
Resolution of this issue is scheduled for alpha2 (around mid to end of
August).
regards,
Lukas Kahwe Smith
[EMAIL
Hi David,
That would be great! Currently I need to call the WSDL-file two times to
be able to handle the exception.
Knut
David Zülke wrote:
I know this is horribly old, but I just stumbled across the same issue
again and realized it has not been tackled yet.
Shouldn't we fix that for 5.3?
Okay, we're taking care of that.
David
Am 23.07.2008 um 22:49 schrieb Lukas Kahwe Smith:
Hi,
Should not be too hard for someone with C knowledge to produce a fix
I would assume. Any takers? Not sure if Dmitry has time for this on
such short notice ..
regards,
Lukas
On 23.07.2008,
I know this is horribly old, but I just stumbled across the same issue
again and realized it has not been tackled yet.
Shouldn't we fix that for 5.3?
David
Am 08.01.2007 um 14:51 schrieb Knut Urdalen:
I agree with Lukas here, currently you have to be proactive against
the location of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Zülke wrote:
I know this is horribly old, but I just stumbled across the same issue
again and realized it has not been tackled yet.
Shouldn't we fix that for 5.3?
David
Am 08.01.2007 um 14:51 schrieb Knut Urdalen:
I agree
Hi,
Should not be too hard for someone with C knowledge to produce a fix I
would assume. Any takers? Not sure if Dmitry has time for this on such
short notice ..
regards,
Lukas
On 23.07.2008, at 20:07, Noah Fontes wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Zülke wrote:
I agree with Lukas here, currently you have to be proactive against the
location of the WSDL-file. I currently do like this in my SoapClient's:
class MySoapClient extends SoapClient {
public function __construct($wsdl ,$options = array()) {
if(is_resource(@fopen($wsdl, 'r'))) {
Hi,
why do I get warnings when I have failures in my ext/soap ctor?
try {
$client = new SoapClient('http://i_dont_exist.com/some.wsdl',
array('exceptions' = true));
} catch (Exception $e) { }
I guess even without the 'exceptions' = true it should always return
all issues as an exception.
14 matches
Mail list logo
