Thanks for the reply.
I did not know you can use expanders for the endpoints too, so thanks a lot for the tip.
-
I resolved the issue regarding the dialogs myself:
Previously, what I did was this:
I created a testcase and teststep on the fly and let that teststep retrieve the wsdl from the service. I then got the response, parsed the wsdl and tried to map the port(s) in the wsdl to interfaces configured in soapui. Then, when found, i updated the endpoints of the interface found so it would point to the right service url. This caused the login popup to show up for services that needed authentication.
Now i do it like this:
I developed a couple of classes that will let me connect to webservices using a HttpURLConnection and by using them, i am bypassing the soapui object tree and the events that come with it ( the dialogs popping up ).
So i am done!
I have a small xml file containing basic information about an environment, including the environment dependend url for the "Service Locator" service, and some properties to use in the testcases.
In my Setup Script, i read the xml, let the user select the environment that he want's to test from an optionDialog and then, based on that choice, retrieve information from the Locator Service, modify the endpoints and set some initial properties.
Thanks,
Evert