Forum Discussion

mwe's avatar
mwe
New Contributor
16 years ago

Failed to load url when using MockService

Hi,

I have a problem with the wsdl that is generated by the MockService when I use the path /Webservice/WS1

Here is what I do.

I have a wsdl and xsd file that I added to a new project in SoapUI. Next I create a MockService for this project and first set the Path for the MockService to /WS1.
I can than view the wsdl in a browser (http://localhost:8080/WS1?WSDL) and view the xsd (http://localhost:8080/WS1?WSDL&interfac ... invoer.xsd).
I than create a new project in SoapUi and add the wsdl-location of the MockService (http://localhost:8080/WS1?WSDL). Everything works ok.

Next I change the Path of the MockService to /Webservice/WS1. Again I can view the wsdl of the new url in the browser (http://localhost:8080/Webservice/WS1?WSDL) and the xsd (http://localhost:8080/Webservice/WS1?WS ... invoer.xsd).
But when I create a new project and add the wsdl from the new url (http://localhost:8080/Webservice/WS1?WSDL) I get an error.
ERROR [WsdlLoader] Failed to load url [http://localhost:8080/Webservice/Webservice/WS1?WSDL&interface=CanonicBindingForStart∂=parkeerinvoer.xsd]
Note that the /Webservice is repeated twice in the url.

When I look at the wsdl in the browser, I see that SoapUi generates the following for the xs:include




The schemaLocation is a relative path, so I would expect it to be  xs:include schemaLocation="WS1?WSDL&interface=CanonicBindingForStart∂=parkeerinvoer.xsd"/>.
Or as an absolute path


I test with the latest release (2.5.1) and the latest nightly build (http://www.eviware.com/nightly-builds/2 ... .2-bin.zip).

Regards,

Micha

3 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    Hi Micha,

    thanks for posting this! Please try the upcoming nightly-build to see if it works better (urls are now absolute)

    regards,

    /Ole
    eviware.com
  • mwe's avatar
    mwe
    New Contributor
    Hi Ole,

    I tested the lates nightlybuild and this bug is indeed fixed.

    Thanks,

    Micha