-
Bug
-
Resolution: Done
-
Major
-
7.2.0.Final
-
None
In 6.0, it was possible to create a leveldb cache configuration like:
<leveldbStore xmlns="urn:infinispan:config:store:leveldb:6.0" location="${user.home}/.komodo/db/data" expiredLocation="${user.home}/.komodo/db/expired" implementationType="JAVA"> </leveldbStore>
Both the location and expiredLocation paths could contain java system properties and these would be substituted when the configuration was parsed. In 7.2, the same configuration successfully substitutes the path attribute but NOT the expiration path attribute:
<leveldb-store xmlns="urn:infinispan:config:store:leveldb:7.2" path="${user.home}/.komodo/db/data"> <expiration path="${user.home}/.komodo/db/expired"/> <implementation type="JAVA"/> </leveldb-store>
Looking at the LevelDBStoreConfigurationParser72 class, the method parseLevelDBCacheStore() (line 55) has a call to:
String value = StringPropertyReplacer.replaceProperties(attributeValue);
while the parseLevelDBCacheStoreExpiry() method does not contain any call. Given the expiry attribute used to be part of the <leveldbStore>, it would seem the replace-properties support has not been carried over into the expiration tag handling.
- blocks
-
MODE-2471 Bug in infinispan cache configuration for leveldb
- Resolved