[infinispan-issues] [JBoss JIRA] (ISPN-4919) Configuration templates

[Paul Ferraro (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024491#comment-13024491 ] 

Paul Ferraro commented on ISPN-4919:
------------------------------------

[~dan.berindei] On the contrary, you lost that behavior in 5.x.
EmbeddedCacheManager.defineConfiguration(String cacheName, String templateCacheName, Configuration configurationOverride)
... behaves exactly the same as:
EmbeddedCacheManager.defineConfiguration(String cacheName, Configuration configuration)
... since the configurationOverride is fully defined - and thus overrides *everything* in the Configuration of the template cache.
Similarly, using the latter method, the Configuration parameter overrides *everything* in the Configuration of the default cache.

> Configuration templates
> -----------------------
>
>                 Key: ISPN-4919
>                 URL: https://issues.jboss.org/browse/ISPN-4919
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Configuration
>            Reporter: Tristan Tarrant
>            Assignee: Tristan Tarrant
>             Fix For: 7.1.0.Beta1
>
>
> Currently there is a 1:1 relationship between configuration and named caches. While the programmatic API does have the ability to .read() an existing configuration to create a new one, the declarative config does not.
> We should introduce the concept of configuration inheritance, e.g.:
> {code}
> <local-cache name="eviction-cache">
>     <eviction strategy="LIRS" maxEntries="10000"/>
> </local-cache>
> <local-cache name="mycache" template="eviction-cache" />
> {code}
> Possibly, cache templates should be made "abstract" so that they cannot be instantiated as named caches directly, e.g.:
> {code}
> <local-cache name="eviction-cache" abstract="true">
> ...
> </local-cache>
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)