Forum Discussion
SteveM
14 years agoOccasional Contributor
Some more info...
I created two demo tests. Test one that logs the info from endpoint and that passes successfully. Test two tries to use the global endpoint and fails.
Test one:
[exec] 09:44:02,823 INFO [SoapUIProTestCaseRunner] running step [Groovy Script]
[exec] 09:44:03,182 INFO [log] endpointValue
Test two:
Status: FAILED
Time Taken: 87
Size: 0
Timestamp: Tue Dec 04 09:44:02 EST 2012
TestStep: Test
----------------- Messages ------------------------------
SubmitException: com.eviware.soapui.model.iface.Request$SubmitException: com.eviware.soapui.impl.wsdl.submit.RequestTransportRegistry$MissingTransportException: Missing protocol in endpoint [${endpoint}]
Now I've also found that if I stop using my custom soapUI-settings xml the endpoint will work correctly. So it seems related to the way that the cmd line runner loads each of the arguements.
I created two demo tests. Test one that logs the info from endpoint and that passes successfully. Test two tries to use the global endpoint and fails.
Test one:
[exec] 09:44:02,823 INFO [SoapUIProTestCaseRunner] running step [Groovy Script]
[exec] 09:44:03,182 INFO [log] endpointValue
Test two:
Status: FAILED
Time Taken: 87
Size: 0
Timestamp: Tue Dec 04 09:44:02 EST 2012
TestStep: Test
----------------- Messages ------------------------------
SubmitException: com.eviware.soapui.model.iface.Request$SubmitException: com.eviware.soapui.impl.wsdl.submit.RequestTransportRegistry$MissingTransportException: Missing protocol in endpoint [${endpoint}]
Now I've also found that if I stop using my custom soapUI-settings xml the endpoint will work correctly. So it seems related to the way that the cmd line runner loads each of the arguements.