composite project interface caching issue
When setting "Cache Definitions" to "false" on a composite project, the interface setting "Cached" stays set to "true" and cannot be changed. When doing the same thing on a non-composite project, the ...
Forum Discussion
The situation can be reproduced quite easily:
1. Create a composite project ("cache definitions" property on project should be "true")
2. Add interface based on WSDL
3. Switch "cache definitions" property back and forth to "false" and "true"
4. Check each time on WSDL interface that "cached" property is also switched -> this doesn't seem to be the case
The problem seems to be just in the UI, because running tests and/or closing and reopening SoapUI does seem to refresh the UI. Also it looks like we don't have actual issues with the caching. It was just confusing us.
1. Create a composite project ("cache definitions" property on project should be "true")
2. Add interface based on WSDL
3. Switch "cache definitions" property back and forth to "false" and "true"
4. Check each time on WSDL interface that "cached" property is also switched -> this doesn't seem to be the case
The problem seems to be just in the UI, because running tests and/or closing and reopening SoapUI does seem to refresh the UI. Also it looks like we don't have actual issues with the caching. It was just confusing us.