[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:all-tabpanel ]

Tristan Tarrant updated ISPN-4919:
----------------------------------
    Description: 
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}

  was:
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.:

<local-cache name="eviction-cache">
    <eviction strategy="LIRS" maxEntries="10000"/>
</local-cache>

<local-cache name="mycache" template="eviction-cache" />

Possibly, cache templates should be made "abstract" so that they cannot be instantiated as named caches directly, e.g.:

<local-cache name="eviction-cache" abstract="true">
...
</local-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.Alpha1
>
>
> 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.1#6329)