Running and demo-ing soapUI 3.6.1.
I believe the proxy here uses a Windows authentication scheme; I guess I don't really understand why that wouldn't be supported.
When I initially set up proxy settings, I was able to connect to the internet.
Then I changed them, then changed them back to the original.
No matter how many times I have saved the information in the UI - or edited prefs.js in the .JxBrowser folder - SoapUI will not connect to the Internet.
I guess I'll have to uninstall and reinstall if I want to add a WSDL outside the company's firewall, say for a sample project.
I think it's really weird that it worked initially, then stopped working.
Seems a lot of work just to get basic functionality up and running. I have to say this doesn't really bode well for our adoption of the tool.