[infinispan-issues] [JBoss JIRA] (ISPN-7095) JCache remote CacheManger needs to be aware of current server state

[Zdenek Hostasa (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-7095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zdenek Hostasa updated ISPN-7095:
---------------------------------
          Description: 
As per ISPN-6574 the JCache API needs to reflect correctly on caches created from outside of this API (in server config for example). This issue was addressed for .getCache method, but remains unfixed for other three methods mentioned in previous request.
*Note:* During test creation I found out that invoking CacheManager.getCache will refresh that particular caches reference in the manager and the rest of the methods work correctly afterwards (for that one cache).

  was:As per ISPN-6574 the JCache API needs to reflect correctly on caches created from outside of this API (in server config for example). This issue was addressed for .getCache and .enableManagement methods, but remains unfixed for other two methods mentioned in previous request, .getCacheNames and .enableStatistics.

    Affects Version/s: 9.0.0.Alpha3
                           (was: 9.0.0.Alpha4)


> JCache remote CacheManger needs to be aware of current server state
> -------------------------------------------------------------------
>
>                 Key: ISPN-7095
>                 URL: https://issues.jboss.org/browse/ISPN-7095
>             Project: Infinispan
>          Issue Type: Bug
>          Components: JCache
>    Affects Versions: 9.0.0.Alpha3
>            Reporter: Zdenek Hostasa
>
> As per ISPN-6574 the JCache API needs to reflect correctly on caches created from outside of this API (in server config for example). This issue was addressed for .getCache method, but remains unfixed for other three methods mentioned in previous request.
> *Note:* During test creation I found out that invoking CacheManager.getCache will refresh that particular caches reference in the manager and the rest of the methods work correctly afterwards (for that one cache).



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)