[infinispan-issues] [JBoss JIRA] Issue Comment Edited: (ISPN-961) Implement a provider for Spring's Cache Abstraction

[ https://issues.jboss.org/browse/ISPN-961?page=com.atlassian.jira.plugin.s... ] Olaf Bergner edited comment on ISPN-961 at 3/7/11 4:29 AM: ----------------------------------------------------------- I published a first attempt at implementing such a provider at https://github.com/obergner/spring-infinispan. Right now, it concentrates on supporting the embedded use case, i.e. when client and Infinispan are colocated within the same JVM. Supporting the hot-rod client for remotely accessing caches has been deferred. Current state of affairs: * Created an implementation of {{org.springframework.cache.Cache}}, backed by {{org.infinispan.Cache}}. * Created an implementation of {{org.springframework.cache.CacheManager}}, backed by {{org.infinispan.manager.CacheContainer}}. * Implemented a Spring {{FactoryBean}} for creating instances of {{org.infinispan.Cache}}. * Implemented a Spring {{FactoryBean}} for creating instances of {{org.infinispan.manager.EmbeddedCacheManager}}. * Implemented a Spring {{FactoryBean}} for creating instances of {{org.infinispan.config.Configuration}}, i.e. the default configuration to be used by an Infinispan {{CacheContainer}} when creating new {{Cache}} instances. Known limitations: * CacheManager-implementation does *not* support programmatically adding new caches at runtime. The list of known caches is initialized once when being instantiated. Caches later added to the backing EmbeddedCacheManager are not visible to the Spring CacheManager. TODO (embedded use case): * Implement a {{FactoryBean}} for creating instances of {{org.infinispan.config.GlobalConfiguration}}. * Implement a {{FactoryBean}} for creating *named* configurations, i.e. configurations to be used for *named* caches. * Improve code coverage. * Improve javadocs, especially package-level javadocs. was (Author: O.Bergner): I published a first attempt at implementing such a provider at https://github.com/obergner/spring-infinispan. Right now, it concentrates on supporting the embedded use case, i.e. when client and Infinispan are colocated within the same JVM. Supporting the hot-rod client for remotely accessing caches has been deferred. Current state of affairs: * Created an implementation of org.springframework.cache.Cache, backed by org.infinispan.Cache. * Created an implementation of org.springframework.cache.CacheManager, backed by org.infinispan.manager.CacheContainer. * Implemented a Spring FactoryBean for creating instances of org.infinispan.Cache. * Implemented a Spring FactoryBean for creating instances of org.infinispan.manager.EmbeddedCacheManager. * Implemented a Spring FactoryBean for creating instances of org.infinispan.config.Configuration, i.e. the default configuration to be used by an Infinispan CacheContainer when creating new Cache instances. Known limitations: * CacheManager-implementation does *not* support programmatically adding new caches at runtime. The list of known caches is initialized once when being instantiated. Caches later added to the backing EmbeddedCacheManager are not visible to the Spring CacheManager. TODO (embedded use case): * Implement a FactoryBean for creating instances of org.infinispan.config.GlobalConfiguration. * Implement a FactoryBean for creating *named* configurations, i.e. configurations to be used for *named* caches. * Improve code coverage. * Improve javadocs, especially package-level javadocs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira