Forum Discussion

egrigoletto's avatar
egrigoletto
Occasional Contributor
13 years ago

Error using apache WSDL

Hi everybody!

I am trying to use SOAPUI to reference a WSDL through a specific URL.
But when I am trying to create a new project I receive the message "Error: type 'Document@http://xml.apache.org/xml-soap' not found".
I used a dh.xsd as proposed at other case that I sought in this forum but doesn't worked.
Someone past through the same situation? If yes, there are some way to avoid this error?

Thanks in advance

7 Replies

  • tjdurden's avatar
    tjdurden
    Frequent Contributor
    13 years ago
    I haven't seen the other post to which you refer, but whilst this may be pretty obvious, this seems less to do with SoapUI itself but potentially due to something invalid in the WSDL which you are trying to import. Does the WSDL successfully validate in an external tool (e.g. XML Spy)? Are you able to attach the schema?
  • egrigoletto's avatar
    egrigoletto
    Occasional Contributor
    13 years ago
    I am sending the WSDL file pasted from a external URL WSDL, I don't have XSD files from this WSDL.
    I saved in a XML extension but is a WSDL file.
    If you need more information, just ask.

    Thanks in advance for your help.
  • tjdurden's avatar
    tjdurden
    Frequent Contributor
    13 years ago
    Hi egrigoletto,

    I was able to replicate your error by attempting to import your attached XML file, so I ran the file through an XML validator, and the error thrown was:
    Invalid XML schema: ''apachesoap:Document' must refer to an existing simple or complex type.'


    If you look at line 189 in your schema, you'll see this:
    <element name="XMLDocument" nillable="true" type="apachesoap:Document"/>


    Basically, the element type is set to "apachesoap:Document", but this type cannot be found within the WSDL.

    Kind regards,
    Tim
  • egrigoletto's avatar
    egrigoletto
    Occasional Contributor
    13 years ago
    Thank you so much for help!

    I understand the error nature and what can be done, but something bothers me.
    This WSDL sent by me is in a URL, referencing this URL the services can be accessed (in simple words, I insert the URL in SOAPUI and try to open this WSDL), is clear the WSDL has a wrong parameter, but considering that I cannot change the WSDL reachable through web, how I can make SOAPUI understand this WSDL? Some parameter can be changed or some setting can be created to allow me to use this WSDL?

    Thank you again, don't you know how much you are helping me
  • tjdurden's avatar
    tjdurden
    Frequent Contributor
    13 years ago
    Hi egrigoletto,

    Perhaps someone else on this forum can correct me if I'm wrong, but whilst I can appreciate your situation, unfortunately, my thoughts are that if the WSDL you are importing is not valid, then there's little more you can do apart from contacting the developer of the WSDL to ask them to make the necessary changes.

    Kind regards,
    Tim