compared with
Current by Jeannie BOFFEL
on May 16, 2012 10:35.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (19)

View Page History
<p>Changes to the Zend_Soap component that may or may not be important to make this component better for the 2.0 release. This has to be split into the 4 subcomponents.</p>

*The <p><strong>The following list is no guaruantee that the features will be included at any time in Zend_Soap* Zend_Soap</strong></p>

h3. Zend_Soap_Client
<h3>Zend_Soap_Client</h3>

h3. Zend_Soap_Server
<h3>Zend_Soap_Server</h3>

<ul>
* Add <li>Add a new Zend_Soap_Server_Autodiscovered that combines Zend_Soap_Server and Zend_Soap_AutoDiscover to listen at one location for server.php and server.php?Wsdl automatically. Can be implemented fairly simple through some kind of proxy/composite pattern mixture.</li>
</ul>

h3. Zend_Soap_AutoDiscover

* Change Constructor to take all dependencies and straighten up their usage.
* Refactor Zend_Soap_AutoDiscover to build WSDL file only in handle() function and not before. Delegate this building to a builder class for simple switching.
* Renaming of ComplexTypes based on a "classmap" like option that hides or simplifies naming of the service related classes in generation for the WSDL file.
* Try the possibility of adding multiple services as specified in WSDL specification.
* Add real XSD generation support via reflection on PHP DocBlock. Something looking like that : [http://framework.zend.com/wiki/display/ZFPROP/Zend_Soap_Wsdl_Strategy_DefaultComplexType+-+Improvement+for+the+AutoDiscover+-+Jeannie+BOFFEL]
<h3>Zend_Soap_AutoDiscover</h3>

h3. Zend_Soap_Wsdl
<ul>
<li>Change Constructor to take all dependencies and straighten up their usage.</li>
<li>Refactor Zend_Soap_AutoDiscover to build WSDL file only in handle() function and not before. Delegate this building to a builder class for simple switching.</li>
<li>Renaming of ComplexTypes based on a &quot;classmap&quot; like option that hides or simplifies naming of the service related classes in generation for the WSDL file.</li>
<li>Try the possibility of adding multiple services as specified in WSDL specification.</li>
<li>Add real XSD generation support via reflection on PHP DocBlock. Something looking like that : <a href="http://framework.zend.com/wiki/display/ZFPROP/Zend_Soap_Wsdl_Strategy_DefaultComplexType+-+Improvement+for+the+AutoDiscover+-+Jeannie+BOFFEL">Improvement for the AutoDiscover</a></li>
</ul>

* Refactor to take work out of the constructor.
* Allowing adding of soap:header tags.
* Implement the WSDL specification more causiously.

<h3>Zend_Soap_Wsdl</h3>

<ul>
<li>Refactor to take work out of the constructor.</li>
<li>Allowing adding of soap:header tags.</li>
<li>Implement the WSDL specification more causiously.</li>
* Split <li>Split rendering the WSDL structure parts from the rendering of the SOAP structure parts, so that the different namespace requirements on their own and can be combined to form the final SOAP-WSDL file.</li>
* Implement <li>Implement a simple WSDL Parser for Unit-Testing purposes and Zend_Tool Code Generation support from WSDL files for SOAP Clients.</li>
</ul>