Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6786853
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T17:17:41+00:00 2026-05-26T17:17:41+00:00

I have taken over support of a web application and it includes a SOAP

  • 0

I have taken over support of a web application and it includes a SOAP web service. The soap server is coded in PHP using SoapServer (http://php.net/manual/en/soapserver.soapserver.php) and works correctly with PHP as the soap client. But now I am trying to use the WSDL in Visual Studio 2010, and although Visual Studio is able to see all the methods defined in the WSDL, when I have attached the web reference the .Net application throws an error when I try to compile. The error that is thrown is as follows:

Custom tool error: Unable to import WebServiceSchema. Unable to import binding ‘ApolloSoap’ from namespace ‘http://clientdomain/soap/export’. Unable to import operation ‘getPosts’. The datatype ‘http://clientdomain/soap/export/:getPostsArray’ is missing.

I will post the source of the WSDL document (Note that I have abridged the source because it is HUGE. I have taken out everything pertaining to other methods in the WSDL to try focus on the method that is reported in the error message.)

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://clientdomain/soap/export/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://clientdomain/soap/export/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    <wsdl:types>
        <s:schema targetNamespace="http://clientdomain/soap/export/" elementFormDefault="qualified">
            <s:import namespace="http://microsoft.com/wsdl/types/"/>
            <s:element name="post">
                <s:complexType>
                    <s:sequence>
                        <s:element minOccurs="1" maxOccurs="1" name="Reference" type="s:string"/>
                        <s:element minOccurs="1" maxOccurs="1" name="Technician" type="s:string"/>
                        <s:element minOccurs="1" maxOccurs="1" name="Customer" type="s:string"/>
                        <s:element minOccurs="1" maxOccurs="1" name="Address" type="s:string"/>
                    </s:sequence>
                </s:complexType>
            </s:element>
            <s:element name="getPosts">
                <s:complexType>
                    <s:sequence>
                        <s:element minOccurs="1" maxOccurs="1" name="authorisationcode" type="s:string"/>
                    </s:sequence>
                </s:complexType>
            </s:element>
            <s:element name="getPostsResponse">
                <s:complexType>
                    <s:sequence>
                        <s:element name="getPostsArray" type="tns:getPostsArray"/>
                    </s:sequence>
                </s:complexType>
            </s:element>
            <s:element name="getPostsArray">
                <s:complexType>
                    <s:complexContent>
                        <s:restriction base="soapenc:Array">
                            <s:attribute ref="soapenc:arrayType" wsdl:arrayType="tns:post[]"/>
                        </s:restriction>
                    </s:complexContent>
                </s:complexType>
            </s:element>
        </s:schema>
    </wsdl:types>
    <wsdl:message name="getPostsSoapIn">
        <wsdl:part name="parameters" element="tns:getPosts"/>
    </wsdl:message>
    <wsdl:message name="getPostsSoapOut">
        <wsdl:part name="parameters" element="tns:getPostsResponse"/>
    </wsdl:message>
    <wsdl:portType name="ApolloSoap">
        <wsdl:operation name="getPosts">
            <wsdl:documentation xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/'>
                    Function ("getPosts")
                </wsdl:documentation>
            <wsdl:input message="tns:getPostsSoapIn"/>
            <wsdl:output message="tns:getPostsSoapOut"/>
        </wsdl:operation>
    </wsdl:portType>
    <wsdl:portType name="ApolloSoap12">
        <wsdl:operation name="getPosts">
            <wsdl:documentation xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/'>
                    Function ("getPosts")
                </wsdl:documentation>
            <wsdl:input message="tns:getPostsSoapIn"/>
            <wsdl:output message="tns:getPostsSoapOut"/>
        </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="ApolloSoap" type="tns:ApolloSoap">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>
        <wsdl:operation name="getPosts">
            <soap:operation soapAction="http://clientdomain/soap/export/getPosts" style="document"/>
            <wsdl:input>
                <soap:body use="literal"/>
            </wsdl:input>
            <wsdl:output>
                <soap:body use="literal"/>
            </wsdl:output>
        </wsdl:operation>
    </wsdl:binding>
    <wsdl:binding name="ApolloSoap12" type="tns:ApolloSoap12">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>
        <wsdl:operation name="getPosts">
            <soap12:operation soapAction="http://clientdomain/soap/export/getPosts" style="document"/>
            <wsdl:input>
                <soap12:body use="literal"/>
            </wsdl:input>
            <wsdl:output>
                <soap12:body use="literal"/>
            </wsdl:output>
        </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="wService">
        <wsdl:port name="ApolloSoap" binding="tns:ApolloSoap">
            <soap:address location="http://clientdomain//web/_soap/server.php?pmoaEyLb3BvW0Vwc3jf="/>
        </wsdl:port>
        <wsdl:port name="ApolloSoap12" binding="tns:ApolloSoap12">
            <soap12:address location="http://clientdomain//web/_soap/server.php?pmoaEyLb3BvW0Vwc3jf="/>
        </wsdl:port>
    </wsdl:service>
</wsdl:definitions>

Can anyone help me figure out what is wrong with this WSDL document and why .Net is not seeing the definition of getPostsArray despite the fact that it is defined in the types section of the document?

UPDATE:

I have a suspicion that the lines causing the problem for visual Studio are the following:

<s:restriction base="soapenc:Array">
    <s:attribute ref="soapenc:arrayType" wsdl:arrayType="tns:post[]"/>
</s:restriction>

I suspect these lines because when I create a simple web service in Visual Studio I see that the generated code for the array is as follows:

<s:complexType name="ArrayOfPost">
    <s:sequence>   
        <s:element minOccurs="0" maxOccurs="unbounded" name="Post" nillable="true" type="tns:Post" />
    </s:sequence>
</s:complexType>

Can anyone explain these two different ways of defining an array of a complex type and confirm/deny that the syntax in my WSDL document is incorrect?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-26T17:17:41+00:00Added an answer on May 26, 2026 at 5:17 pm

    Visual Studio is telling you the truth. Here’s what XMLSpy says:

    File Untitled1.wsdl is not valid.
    Invalid XML schema: ”tns:getPostsArray’ must refer to an existing simple or complex type.’

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have taken over support of a VB .Net application that makes use of
I have taken over support of a VB.Net WinForms application. I am actually a
I have taken over support of an application at the company I work for.
We have taken over some .NET 1.1 Windows Service code that spawns threads to
I am developing a web application using Python, Django and MySql. I have a
I've taken over an application using linq-to-sql and now plan to do some major
I have taken over the maintenance of an application that uses a stax parser
I've taken over support of a legacy web app written predominantly in classic ASP.
I recently have taken the support and programming of a web system written in
I am taken over support on a VB.Net WinForms application and the company that

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.