I just tried it with a clean project with SoapUI-Pro 4.6.1. This is definitely still broken!
If I go further, and use the workaround as above (open and close the JDBC step) and then try to run against the previous environment it uses the updated credentials. The workaround mentioned in my reply way above still works tho'.
You can confirm this by using composite project. Set everything up as I mentioned. When you exist SoapUI in step 5, backup the test file. When you perform the workaround in step 9, exit again. Compare the two test files - you will notice everything inside is hard-wired!!!
