[
https://issues.jboss.org/browse/ISPN-905?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño commented on ISPN-905:
---------------------------------------
Patrick, could you please provide use cases for each of this operations so that we can
understand better the meaning/aim of them?
For example, why do you need cacheExists()/getCacheIfExists()? I assume that it'd
return true only if a cache with that name has been started. If stopped it'd returned
false. Whether the cache is defined or not in the config would have no bearing here.
Wrt remove(), would not cache.stop() be enough for you? For example, stopping a cache
removes all its contents. The only thing that cache.stop() could not do but
CacheManager.remove() could, would be to update CacheManager's caches collection.
Your comment wrt remove() being transaction safe is also something that should prob affect
cache.stop() as well. In fact, I think this should be separated into a diff jira.
FAO Manik, do you have any background information for this? For some reason it rings a
bell that something related to this was discussed in dev/user forums but cannot find the
link right now.
Enhance cache management methods on EmbeddedCacheManager
--------------------------------------------------------
Key: ISPN-905
URL:
https://issues.jboss.org/browse/ISPN-905
Project: Infinispan
Issue Type: Feature Request
Components: Core API
Affects Versions: 4.2.0.Final
Reporter: Patrick McFarland
Assignee: Galder Zamarreño
Fix For: 5.0.0.ALPHA3, 5.0.0.Final
These should include:
{code:borderStyle=solid}
boolean cacheExists(String cache)
Cache<?, ?> getCacheIfExists(String cache)
boolean remove(String Cache)
{code}
Original request:
{quote}
There seems to be no ability to check if a populated cache exists through both
CacheManager and through Cache (=is this still a valid handle) and to get a cache if it
exists.
{quote}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira