Microsoft Knowledge Base Email Alertz

(889494) - Discusses a problem that occurs when you generate a schema from a WSDL file. The correct XSD code is not generated when a part has a type reference in Office InfoPath 2003.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 889494 - Last Review: September 22, 2011 - Revision: 3.0

InfoPath 2007 and InfoPath 2003 cannot correctly generate a form when a WSDL file uses definitions with a type reference

SYMPTOMS

You 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 2007 and 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"

CAUSE

This problem occurs because InfoPath does not generate the correct XSD code when a part has a type reference. SOAP returns an empty Message name value.

RESOLUTION

Microsoft 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.

APPLIES TO
  • Microsoft Office InfoPath 2007
  • Microsoft Office InfoPath 2003
Keywords: 
kbpending kbprogramming kbtshoot kbbug KB889494
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate