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

[Tristan Tarrant (JIRA)]

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

Tristan Tarrant commented on ISPN-4919:
---------------------------------------

Here is the latest proposal (from a short chat I've had with [~pferraro] on IRC:

- add a <[local|replicated|distributed|invalidation]-cache-configuration name="..." [extends="..."]?> for defining configurations
- keep the current <[local|replicated|distributed|invalidation]-cache> elements which keep a 1:1 relationship between caches and configurations, also allowing optional "configuration" attribute
- add a <caches names="name1 name2 ..." configuration="..." /> element for multi-cache declarations.

Constraints:
- make sure that the cache mode is "compatible" in the inheritance chain (i.e. a distributed-cache-configuration cannot extend a local-cache-configuration)

> 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
>
> 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.11#6341)