I don't quite understand your question. A type referenced from a <wsdl:part> definition must reference a type defined in a schema that is defined in the <wsdl:types> section. The type cannot be defined using <wsdl:part> definitions.
In your two examples, the response messages on the wire would look something like this:
1: <soap:Body>
<ns1:accountSetParametersResponse xmlns:ns1="[namespace-uri]">
<accountSetParametersReturn>
... (content of type "intf:AccountSetParametersResponse")
</accountSetParametersReturn>
</ns1:accountSetParametersResponse xmlns:ns1="[namespace-uri]">
</soap:Body>
2: <soap:Body>
<ns1:accountSetParametersResponse xmlns:ns1="[namespace-uri]">
<accountSetParametersReturn>
... (content of type "intf:AbmResponse")
</accountSetParametersReturn>
<m_subscriptionIdList>
... (content of type "intf:SubscriptionIdList")
</m_subscriptionIdList>
</ns1:accountSetParametersResponse xmlns:ns1="[namespace-uri]">
</soap:Body>
On 12/13/06, Alper Aykac <aykacalper@...> wrote:
Hi,what is the difference between two following wsdl lines ;1.) AccountSetParametersResponse is a complex type which includes 2 wsld:parts in second line (accountSetParametersReturn and m_subscriptionIdList... both of which are different types as you can see..)<wsdl:message name="accountSetParametersResponse">
<wsdl:part name="accountSetParametersReturn" type="intf:AccountSetParametersResponse"/>
</wsdl:message>
2.)
<wsdl:message name="accountSetParametersResponse">
<wsdl:part name="accountSetParametersReturn" type="intf:AbmResponse"/>
<wsdl:part name="m_subscriptionIdList" type="intf:SubscriptionIdList"/></wsdl:message>brAlper