<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[

<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[

Zend Framework: Zend_Soap_AutoDiscover Component Proposal

Table of Contents

1. Overview

Adding complex array structure to WSDL generated by Zend_Soap_Wsdl and Zend_Soap_AutoDiscover.

Some people use WSDL as the webservice API documentation. WSDL that shows just "array" as input or output request doesn't help the client side team. This proposal may provide additional information to WSDL when server side wants to work with array. The major goal is to answer the commom question: what does this array contain? an integer? an string?

2. References

• http://www.w3.org/2002/ws/databinding/edcopy/advanced/advanced.html#pattern-SOAPEncodedArray
• http://www.w3.org/2002/ws/databinding/examples/6/09/SOAPEncodedArray/
• http://www.w3.org/TR/wsdl#_types

3. Component Requirements, Constraints, and Acceptance Criteria

• This proposal must provides an easy way to declare multi-dimensional arrays in webservices classes
• Current Zend_Soap_AutoDiscover and Zend_Soap_Wsdl behavior still must work for "@param array" and "@return array"

4. Dependencies on Other Framework Components

No dependency.

5. Theory of Operation

Users just will have to use new documentation style into their webservices classes.

6. Milestones / Tasks

• Milestone 1: design
• Milestone 2: tests
• Milestone 3: documentation

7. Class Index

No new class is necessary.

8. Use Cases

WSDL must contain in "message" part:

WSDL must contain in "types" part:

WSDL must contain in "message" part:

WSDL must contain in "types" part:

WSDL must contain in "message" part:

WSDL must contain in "types" part:

9. Class Skeletons

No new class is necessary, zf core team have to change Zend_Soap_Wsdl and Zend_Soap_AutoDiscover internal methods.