Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81535 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 9261 invoked from network); 1 Feb 2015 17:51:40 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Feb 2015 17:51:40 -0000 Authentication-Results: pb1.pair.com smtp.mail=martin@divbyzero.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=martin@divbyzero.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain divbyzero.net from 87.230.111.149 cause and error) X-PHP-List-Original-Sender: martin@divbyzero.net X-Host-Fingerprint: 87.230.111.149 mx.bauer-kirch.biz Linux 2.6 Received: from [87.230.111.149] ([87.230.111.149:53662] helo=mx.bauer-kirch.biz) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 01/81-33325-BA76EC45 for ; Sun, 01 Feb 2015 12:51:40 -0500 Received: from xdsl-87-78-44-2.netcologne.de ([87.78.44.2] helo=cuda.lan.divbyzero.net) by mail.bauer-kirch.de with ESMTPSA id 1YHygK-0002sL-PO authenticated id <420000403> (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) for ; Sun, 01 Feb 2015 18:51:36 +0100 Message-ID: <54CE67A7.90607@divbyzero.net> Date: Sun, 01 Feb 2015 18:51:35 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: internals@lists.php.net References: <54CE53E7.7040205@divbyzero.net> In-Reply-To: <54CE53E7.7040205@divbyzero.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] PHP 7: Odd behavior with exp/soap From: martin@divbyzero.net (Martin Jansen) On 01.02.15 17:27, Martin Jansen wrote: > Currently I'm seeing some odd behavior with PHP 7 and SoapClient > embedded deep into a Symfony2 application. That same code works with > 5.x. Unfortunately I cannot yet reproduce the issue with a short script. Please ignore that one; I ran into the problem with 5.x as well and it turned out that the problem was in the application itself. Sorry for the noise. - Martin