Skip to end of metadata
Go to start of metadata

<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>

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

<h3>Zend_Soap_Client</h3>

<h3>Zend_Soap_Server</h3>

<ul>
<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</h3>

<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 "classmap" 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>

<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>
<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>
<li>Implement a simple WSDL Parser for Unit-Testing purposes and Zend_Tool Code Generation support from WSDL files for SOAP Clients.</li>
</ul>

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Nov 12, 2009

    <p>I would like to see some more enhancements on the Zend_Soap_Client side to support WSE. Maybe i can contribute that .. <ac:emoticon ac:name="smile" /> (Used in one of my Proposed Zend_Service_* Components)</p>

  2. Dec 17, 2009

    <p>Maybe implement WS-Security? it's really a PITA to work with wso2 extension :S</p>

  3. Jan 04, 2010

    <p>WS Security is also my greatest wish for Zend_SOAP 2.0. A Zend_SOAP_WSSecurity that at least implements the basic authorization techniques would be a great improvement, and would give us the ability to use Zend_SOAP to a much greater extent. </p>

  4. Feb 12, 2010

    <p>WSDL is not limited to SOAP so I think it should be Zend_Wsdl.</p>

  5. Oct 07, 2010

    <p>Yes. I am directed to here when I am studying Zend_Soap_Server and find that Zend_soap_server does not have built-in WS security support. Zend_Soap_Server is just a wrapper of PHP SOAP extension. I wish Zend_Soap_Server can support WS security soon as, without support of WS Security, we will doubt using PHP to make WS server in enterprise application. I think Java world has such implementation for years. For example, apache.org has Axis2 and WSS4J. Can Zend Framework have similar things? </p>