| Geoffrey Carter 2005-06-17, 5:51 pm |
| Can anyone help with this problem? I have an orchestration exposed as a WS.
When I try to design an InfoPath form using the WS I get this error:
WSDLOperation:Type conflict for part (part) HRESULT=0x80070057: The
parameter is incorrect.
- WSDLOperation:Initializing of the output message failed for operation
SOAPReceiveQuote HRESULT=0x80070057: The parameter is incorrect.
- WSDLPort:An operation for port
ValidationQuote_Orchestration_Quote_Rece
iveQuoteWSPortSoap could not be
initialized HRESULT=0x80070057: The parameter is incorrect.
- WSDLPort:Analyzing the binding information for port
ValidationQuote_Orchestration_Quote_Rece
iveQuoteWSPortSoap failed
HRESULT=0x80070057: The parameter is incorrect.
- WSDLService:Initialization of the port for service
ValidationQuote_Orchestration_Quote_Rece
iveQuoteWSPort failed
HRESULT=0x80070057: The parameter is incorrect.
- WSDLReader:Analyzing the WSDL file failed HRESULT=0x80070057: The
parameter is incorrect.
I have a "labs" example installed which works perfectly with InfoPath. I
think it is the WSDL which is causing the issue. The top of the WSDL for my
orchestration looks like this:
- <wsdl:types>
- <s:schema elementFormDefault="qualified"
targetNamespace="http://Validator">
- <s:element name="SOAPReceiveQuote">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="part"
type="tns:Global_LDi_Quote_Inbound" />
</s:sequence>
</s:complexType>
</s:element>
- <s:complexType name="Global_LDi_Quote_Inbound">
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="Header"
type="tns:Global_LDi_Quote_InboundHeader" />
<s:element minOccurs="0" maxOccurs="1" name="Detail"
type=" tns:ArrayOfGlobal_LDi_Quote_InboundVendo
r" />
</s:sequence>
</s:complexType>
which is very different from the WSDL from the labs example:
- <wsdl:types>
- <s:schema elementFormDefault="qualified" targetNamespace="http://BTSDG">
<s:import namespace="http://BTSDG_BusCards.Requisition" />
<s:import namespace="http://BTSDG_BusCards.Confirmation" />
- <s:element name="ReceiveRequisition">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" ref="s1:Requisition" />
</s:sequence>
</s:complexType>
</s:element>
- <s:element name="ReceiveRequisitionResponse">
- <s:complexType>
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" ref="s2:Confirmation" />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
It must be something in my schema although the orchestration works without
any issues when activated through a file receive function. Any help would
be appreciated.
Geoffrey Carter
|