By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,983 Members | 1,597 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,983 IT Pros & Developers. It's quick & easy.

SOAP complexTypes

P: n/a
I have a wsdl definition that includes the following definition for
the element <Preferencesinside the request createFooBar:

<xs:element minOccurs="1" name="Preferences" nillable="true"
type="java1:List" xmlns:java1="java:java.util"/>
....
<xs:schema attributeFormDefault="unqualified"
elementFormDefault="qualified" targetNamespace="java:java.util"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://schemas.xmlsoap.org/soap/encoding/"
schemaLocation=""/>
<xs:complexType name="List">
<xs:complexContent>
<xs:restriction base="soapenc:Array" xmlns:soapenc="http://
schemas.xmlsoap.org/soap/encoding/"/>
</xs:complexContent>
</xs:complexType>
</xs:schema>
When building an example createFooBar request using SOAP UI
(www.soapui.org), an example <Preferenceselement is defined like so:
<java1:Preferences soapenc:arrayType="?" soapenc:offset="?" id="?"
href="?"/>

Is anyone familiar with SOAP elements like this?
Should the attributes be read as:
- arrayType: The structure of the array in question.
- offset: The index of the array to consider as index 0.
- id: The index of the array that contains the data we want.
- href: The URI where the array is located.

Many thanks

Andrew
Jan 16 '08 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.