Caching issues - Environment Testings
We have a composite project with different environments (testing, staging) set up, and the default is testing environment. The two environments have different end points and JDBC connections (differe...
Forum Discussion
SmartBear_Suppo
Alumni
AlumniHi,
I have found the issue, it's not a caching issue. The JDBC connection that is being used in your "staging" environment is in fact the connection defined in your default environment. I only had that problem when using the TestRunner. Though project properties are pulled correctly from the specified environment (ex: "staging"), the JDBC connection comes from the default environment. I have logged the bug to the attention of our developers (SOAP-3149).
Regards,
Giscard
SmartBear Support
I have found the issue, it's not a caching issue. The JDBC connection that is being used in your "staging" environment is in fact the connection defined in your default environment. I only had that problem when using the TestRunner. Though project properties are pulled correctly from the specified environment (ex: "staging"), the JDBC connection comes from the default environment. I have logged the bug to the attention of our developers (SOAP-3149).
Regards,
Giscard
SmartBear Support