[
https://issues.jboss.org/browse/ISPN-4919?page=com.atlassian.jira.plugin....
]
Ion Savin commented on ISPN-4919:
---------------------------------
I think a mix of the two would make it easier to read the config: using
<local-cache-template/> (no confusion about the cache not being instantiated because
of the abstract flag) and referring from <local-cache/> to the template (looking at
the local-cache element it's clear that additional configuration elements could be
inherited, no need to look at the local-cache-templates).
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.:
<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>
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)