19 Mar
2010
19 Mar
'10
6:36 p.m.
On Fri, Mar 19, 2010 at 6:08 PM, Vincent Massol <vincent(a)massol.net> wrote:
Proposed Solution:
===============
1) Look for a system property (e.g. xwiki.config.dir) defining a directory location and
if defined look for the files in it using File IO (I know it's not JEE kosher but
it's acceptable IMO). Could be relative or absolute.
2) If not found, look for a JNDI property that gives the location of the config
directory
3) If not found, look for config files in [user.home]/.xwiki
4) If not found, emit an error explaining how to configure xwiki
We could keep the config files in the WAR and fallback on them, WDYT ?
It would have an interesting side effet, some could only overwrite a
couple of config entries in ~/.xwiki/xwiki.cfg and leave the other
entries up to the xwiki.cfg bundled with the WAR (which could evolve
between releases).