Edit report at https://bugs.php.net/bug.php?id=45282&edit=1

 ID:                 45282
 Comment by:         pumuckel at metropolis dot de
 Reported by:        Martin dot Bosslet at googlemail dot com
 Summary:            SoapClient has namespace issues when WSDL is
                     distributed
 Status:             Verified
 Type:               Bug
 Package:            SOAP related
 Operating System:   *
 PHP Version:        5.*, 6CVS (2009-04-28)
 Block user comment: N
 Private report:     N

 New Comment:

Any progress on this issue?


Previous Comments:
------------------------------------------------------------------------
[2008-12-12 18:13:38] clwells at nocworx dot com

This WSDL exhibits this behavior:

http://www.swsoft.com/webservices/vza/4.0.0/VZA.wsdl

------------------------------------------------------------------------
[2008-06-16 15:54:52] Martin dot Bosslet at googlemail dot com

Description:
------------
I have tried to access a web service whose WSDL is distributed among several 
files each of which contains references to several further XSDs. Now the WSDL 
itself is valid, as .NET or Java clients have accessed the services without any 
problems. But when creating a new instance of SoapClient it fails because I'm 
told that a certain element has already been defined. The problem is, that 
there are <message> elements with the same name, but they DO differ in 
namespaces.

Reproduce code:
---------------
$client = new SoapClient('someURI');

/* Please email me to get a copy of the WSDLs producing the error. They're too 
large to be posted here (although I tried to keep them small already) and I 
have no facility to make them available online. */

Expected result:
----------------
No error when parsing the WSDL.

Actual result:
--------------
SoapFault exception: [WSDL] SOAP-ERROR: Parsing WSDL:  '<Element>' already 
defined in <FILE>


------------------------------------------------------------------------



-- 
Edit this bug report at https://bugs.php.net/bug.php?id=45282&edit=1

Reply via email to