-
Bug
-
Resolution: Done
-
Major
-
4.0.0.CR2
-
None
-
Workaround Exists
-
-
Medium
Currently the WAR file we build and distribute uses a static cache configuration, embedded in the WAR file. We need to think of a way to have this configurable. One idea would be to ship with, say, 5 different config files in the WAR:
- cache-local.xml
- cache-dist-sync.xml
- cache-dist-async.xml
- cache-repl-sync.xml
- cache-repl-async.xml
... and the servlet starts the appropriate config based on JVM params (eg., -Dinfinispan.server.rest.cfg=cache-local.xml)
Also, cache-local.xml should be the default since running the WAR file with incorrect or inappropriate cluster settings prevents startup.
Finally perhaps there should be a way to customise the cfg even further - perhaps the default web page could offer a way to upload a config file and restart the cache using this instead?