[dev] wsdl complextypes

[John Morrissey]

Hi Vijay--

On Fri, Apr 21, 2006 at 01:45:22PM +0200, Vijay Mahrra wrote:
> How difficult would it be to add the functionality to create/return/handle
> complex types?  I'm still trying to understand how it all fits together (the
> auto-generated wsdl) at the moment but any pointers would be a great help.

You can define complex types in the $_types array; here's an example from an
application I have:

$_types = array(
    'attrValues' => array('attr'   => 'string',
                          'values' => '{urn:horde}stringArray'),
    'attrValuesArray' => array(array('item' => '{urn:horde}serviceman_attrValues')),
);

which automagically generates this WSDL:

<complexType name="serviceman_attrValues">
	<all>
		<element name="attr" type="xsd:string"/>
		<element name="values" type="tns:stringArray"/>
	</all>
</complexType>
<complexType name="serviceman_attrValuesArray">
	<complexContent>
		<restriction base="SOAP-ENC:Array">
			<attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="tns:serviceman_attrValues[]"/>
		</restriction>
	</complexContent>
</complexType>

> Is anyone on the list working with the rpc interface, whether through soap
> or rest or whatever?  Anyone have any experience of successfully accessing
> the generated horde wsdl with non-php clients?

FWIW, we receive several thousand SOAP transactions through our Horde-based
application every day. The remote end is a J2EE application using the Axis
toolkit.

If you have any more questions, feel free to holler (preferably on-list, for
the benefit of the archives :-)

john
-- 
John Morrissey          _o            /\         ----  __o
jwm at horde.net        _-< \_          /  \       ----  <  \,
www.horde.net/    __(_)/_(_)________/    \_______(_) /_(_)__