BUG: Office InfoPath 2003 cannot correctly generate a form when a WSDL file uses definitions with a type reference (889494)
The information in this article applies to:
- Microsoft Office InfoPath 2003, Service Pack 1 (SP1)
- Microsoft Office InfoPath 2003
SYMPTOMSYou may have a Web Service Description Language (WSDL) file for a Web service that uses definitions with the following attributes: - A type attribute that is similar to the following:
<message name="GetReturnXmlNodeSoapOut">
<part name="XmlNoder" type="s0:myType" />
</message> - An element attribute that is similar to the following:
<message name="GetReturnXmlNodeSoapOut">
<part name="parameters" element="s0:GetReturnXmlNodeResponse" />
</message>
With this WSDL file, Microsoft Office InfoPath 2003 cannot correctly generate a form from the Web service method and you may receive an error message that is similar to the following: "/schema/element[1][@name='myFields']/complexType[1]/sequence[1]/element[2]
[@name='dataFields']/complexType[1]/sequence[1]/element[1]
Undeclared XSD element: {http://tempuri.org/}XmlNoder"
CAUSEThis problem occurs because InfoPath 2003 does not generate the correct XSD code when a part has a type reference. SOAP returns an empty Message name value.RESOLUTIONMicrosoft regularly releases software updates to address specific problems. If Microsoft releases a software update to resolve this problem, this article will be updated with additional information.STATUS Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
| Modification Type: | Major | Last Reviewed: | 1/18/2005 |
|---|
| Keywords: | kbpending kbProgramming kbtshoot kbbug KB889494 kbAudDeveloper |
|---|
|