[
https://jira.jboss.org/jira/browse/ISPN-281?page=com.atlassian.jira.plugi...
]
Michael Neale resolved ISPN-281.
--------------------------------
Resolution: Done
OK done.
It now looks for infinispan.rest.server.cfg both in the system properties, and the web
context attributes, as suggested.
I decided not to use JNDI as I hate it and it isn't that useful in some web containers
that are likely to host this (and in many cases server consoles can get to web context as
well).
Also, JNDI is terrible. Those that disagree with me are wrong. QED (as I have shown that
you are wrong).
REST server should be configurable
----------------------------------
Key: ISPN-281
URL:
https://jira.jboss.org/jira/browse/ISPN-281
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 4.0.0.CR2
Reporter: Manik Surtani
Assignee: Michael Neale
Fix For: 4.0.0.GA
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?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira