Issue Type: Improvement Created: 2009-06-19T03:36:02.000+0000 Last Updated: 2012-11-20T20:53:18.000+0000 Status: Closed Fix version(s): Reporter: Ronny Srnka (spako) Assignee: None Tags: - Zend_Soap_Server
Related issues: Attachments:
Not sure if this is a bug, new feature or improvement...
I have come across an incompatibility that the Soap Server has with the .NET Soap Client. When loading a WSDL generated by Zend_Soap_Autodiscover as a Web Reference in Visual Studio, if there are no objects/complex types in the WSDL signature, then that WSDL is not loaded successfully. I found that the problem is when "types" tag and "xsd:schema" tag, inside that, is missing from the WSDL. It must be there and empty at the least:
I found that putting a call to $this->addSchemaTypeSection(); in the Zend_Soap_Wsdl::__construct() fixed this.
Is this seen as a bug in Visual Studio or is it a shortcoming of Zend_Soap_Autodiscover and Zend_Soap_Wsdl? And either way should there not be a work around to ensure compatibility with .NET?
In our company we have to be sure that our web services are consumable (and easy to use) by .NET clients. For now my work around will be to have a dummy method that has an object as a parameter, though this is not optimal.
Posted by Rob Allen (rob) on 2012-11-20T20:53:18.000+0000
Bulk change of all issues last updated before 1st January 2010 as "Won't Fix".
Feel free to re-open and provide a patch if you want to fix this issue.
Have you found an issue?
See the Overview section for more details.