Better interoperability for generated WSDL with .net client generation tools

[weierophinney]

This issue has been moved from the zendframework repository as part of the bug migration program as outlined here - http://framework.zend.com/blog/2016-04-11-issue-closures.html

---

Original Issue: https://api.github.com/repos/zendframework/zendframework/issues/7196
User: @micheleorselli
Created On: 2015-02-08T19:20:26Z
Updated At: 2015-11-06T20:55:25Z
Body
Lately I worked on exposing SOAP WS to .net client. On the .net side the client classes were generated using the command line tool svcutil.exe which caused some troubles on getting the wsdl right: I needed to add a couple of tweaks to get class generation working as expected.

For this reason I propose two changes:

• add elementFormDefault="qualified" as attribute of <schema> tag (see Zend\Soap\Wsdl::addSchemaTypeSection
• make the maxOccours attribute value for sequence elements configurable. As now it's hardcoded to "unbounded" (see Zend\Soap\Wsdl\ArrayOfTypeSequence::_addSequenceType)

Some information of the constraints imposed by .net tools can be found here: https://msdn.microsoft.com/en-us/library/ms733112.aspx

If there's interest on integrating that stuff I'm willing to create a PR

---

---

Originally posted by @GeeH at zendframework/zend-soap#26

[weierophinney]

This package is considered feature-complete, and is now in security-only maintenance mode, following a decision by the Technical Steering Committee.
If you have a security issue, please follow our security reporting guidelines.
If you wish to take on the role of maintainer, please nominate yourself

If you need an actively developed SOAP client, we recommend phpro/soap-client.