Forum Discussion

ibridge's avatar
ibridge
Occasional Contributor
12 years ago

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 interface setting does change to "false".

We are using SoapUI 5.0 and as we are working with multiple people on the projects using subversion, we actually need composite projects.

Is this a known bug?

5 Replies

  • ibridge's avatar
    ibridge
    Occasional Contributor
    12 years ago
    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.
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    12 years ago
    Hello,

    I have not been able to reproduce this in our latest version 5.1.2, please download this version and check if the issue persists. Thanks.

    Regards,
    Temil
  • ibridge's avatar
    ibridge
    Occasional Contributor
    12 years ago
    As far as we can see this caching problem indeed no longer exists in 5.1.2, but this version has another (bigger) problem regarding Composite Projects.

    See this post.