No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

[2011-02-11 08:23 UTC] ujl at topdanmark dot dk

Hello,
I've same problem. I'm using a WSDL generator which read the WSDL file and the extension doesn't work. I've tried with windows PHP 5.2.17 and PHP 5.3.5. Is the problem solved on the *nix platform and not Windows?
The problem is extactly the same as described by oamblet 2008-07-01 and I didn't understand the issue is not solved in the windows version of PHP??

[2011-07-19 18:33 UTC] abel dot silva at gmail dot com

Hello,
I'm having exactly the same problem.
php 5.3.0 on windows

[2012-05-11 11:40 UTC] patkoscsaba at syneto dot net

I can confirm this bug is still present with PHP 5.3.10 on OpenIndiana.

[2012-08-20 02:00 UTC] bkfake-php at yahoo dot com

I've just encountered this bug/shortcoming.
Thought it deserved a "bump"
the original report from 4 years ago states this bug makes it "hard".
I think the mor accurate word is "impossible"

Still not working. On WIN and Linux PHP 7.1 and 7.2 i have the same problem at now

[2018-07-13 15:43 UTC] code at joshua-behrens dot de

After debugging through the source code of the php soap extension I found the behaviour locked down onto the namespaces. The given example from oamblet works perfectly if the posted schema has a different targetNamespace than the wsdl.
Although the output refers the parent as a property with an underscore as name.
After reading the RFC for WSDL 2.0 I was still clueless whether this behaviour is correct. I assume not as the WSDLs of the SOAP services I usally request share the same namespace with their schemes.
Would allowing the same namespace be correct?