Forum Discussion
kmassagli
14 years agoOccasional Contributor
Hi Ole,
The issue is that the Endpoint URL is not blank. Even a valid response is returned back as shown in the SOA transaction log. What seems to be problem is that a Project property is used to populate the Endpoint for the request. The property is defined in the Project-scope. When I insert a value in the property and run the request via GUI - the request works.
However when I pass the property in via command line, it fails with MalformedURLException. It did not fail initially, but the failure seems to occur after I open the Project in Composite mode, and then save it as a flat-file, then reopen it. This seems to be a contributing factor to reproducing this defect, and gets the project into a weird state.
I reproduced 2 runs:
A. A Failing run (with the MalformedURLException) at 12:07pm where the Property value is passed into the command-line. The property is referenced in the SOA request endpoint.
B. A Passing run (no exception encountered) at 12:10pm where the SOA request endpoint is hardcoded - while the property is still passed in, request does not reference the property - it is a hardcoded string.
I have zipped and attached artifacts from 2 command-line runs:
1. the Project itself,
2. The output consoles
3. SOA Transaction logs
In hopes that you can pinpoint the issue.
Command line used is in the consoleout logs.
I am licensed user of SoapUI Pro
Currently using version:
soapUI Pro 3.6.1, copyright (C) 2007-2010 eviware software ab http://www.soapui.org | http://www.eviware.com Build dist-118-2010-10-18, Build Date 2010/10/18 15:
The issue is that the Endpoint URL is not blank. Even a valid response is returned back as shown in the SOA transaction log. What seems to be problem is that a Project property is used to populate the Endpoint for the request. The property is defined in the Project-scope. When I insert a value in the property and run the request via GUI - the request works.
However when I pass the property in via command line, it fails with MalformedURLException. It did not fail initially, but the failure seems to occur after I open the Project in Composite mode, and then save it as a flat-file, then reopen it. This seems to be a contributing factor to reproducing this defect, and gets the project into a weird state.
I reproduced 2 runs:
A. A Failing run (with the MalformedURLException) at 12:07pm where the Property value is passed into the command-line. The property is referenced in the SOA request endpoint.
B. A Passing run (no exception encountered) at 12:10pm where the SOA request endpoint is hardcoded - while the property is still passed in, request does not reference the property - it is a hardcoded string.
I have zipped and attached artifacts from 2 command-line runs:
1. the Project itself,
2. The output consoles
3. SOA Transaction logs
In hopes that you can pinpoint the issue.
Command line used is in the consoleout logs.
I am licensed user of SoapUI Pro
Currently using version:
soapUI Pro 3.6.1, copyright (C) 2007-2010 eviware software ab http://www.soapui.org | http://www.eviware.com Build dist-118-2010-10-18, Build Date 2010/10/18 15: