[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=13024425#comment-13024425 ] 

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

I think the concept of inheritance is pretty obvious, regardless of what XML Schema's mechanism for "default" attribute values means, and I don't believe anybody would be confused by that. 
The issue at the moment is that in Infinispan's ConfigurationBuilders, most values use primitives which do not semantically carry the concept of default/overridden which is something [~dan.berindei] suggested to fix by using some kind of Value wrapper object (similar to the DMR's ModelNode)

> 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)