Contributions
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, Micha2.5KViews0likes3CommentsRunning Testcase multiple times takes longer to finish
I have created a TestCase in SoapUI for my project. It contains only one teststep. When running this in the UI (on windows) everything goes fine. Running this from the commandline (on windows) everything goes fine as well. But running this from the commandline on a Linux machine shows some strange behavior. The first run: [SoapUITestCaseRunner] soapUI suite [TestSuite] finished in 1273ms The Second run: [SoapUITestCaseRunner] soapUI suite [TestSuite] finished in 107620ms Thrid run: [SoapUITestCaseRunner] soapUI suite [] finished in 112608ms While the testcase itselfs always takes less than a second: [SoapUITestCaseRunner] Finished running soapUI testcase [TestCase], time taken: 255ms, status: FINISHED When I wait 2 minutes, and then run the test again, it is back to a less than 2 seconds. The webservice itself runs on the Linux machine, so from windows I connect to a remote ws, while the testing on Linux connects to localhost. Anybody any idea why testing on Linux shows this strange behavior. Environment: SoapUI: 2.5.1 Windows: xp - sp1 Linux: SUSE LINUX Enterprise Server 9 (i586), VERSION = 9, PATCHLEVEL = 21.4KViews0likes2Comments