Already used sth. similar to the second approach, but using the admin
console (see my previous posts). My problem was partly caused by the
fact, that the needed property was undocumented - Juan already fixed that.
Kind regards
Peter
Am 12.02.19 um 21:13 schrieb Jürgen Weber:
a) create a wildfly resource module:
https://developer.jboss.org/thread/219956?_sscc=t
and make it global:
https://docs.jboss.org/author/display/WFLY10/Subsystem+configuration?_sscc=t
b) or use the -Djspwiki.custom.config=/java/JSPWiki/jspwiki-custom.properties"
Am Mo., 11. Feb. 2019 um 23:24 Uhr schrieb Peter Nabbefeld
<peter.nabbef...@gmx.de>:
Hello,
I've installed JspWiki on JBoss Wildfly, but I cannot figure out where
to put the configuration file.
Wildfly is running in standalone mode as its own user, so JspWiki is
deployed in
/opt/wildfly/standalone/tmp/vfs/deployment/deploymentxxxxxxx/jspwiki-main-2.11.0.M1.jar-yyyyyyy
Temporary files are deleted on disable, so it seems a bad idea to put
any configuration files there. I've tried to put
jspwiki-custom.properties into /opt/wildfly/appclient/configuration/,
but it seems not to be used, as well as the one created by Install.jsp
script (checked after restart using "ll -u").
BTW, wiki files are properly stored under /opt/wildfly/jspwiki-files.
The only possible options I'm currently aware of:
1. Setting java.io.tmpdir - why is /tmp used for a properties file?
IMHO, mixing configuration with temporary data isn't a good idea, but
probably I'm just missing sth.
2. Adding a deployment overlay
(https://docs.jboss.org/author/display/WFLY8/Deployment+Overlays). While
this seems at least a bit better, I'll have to "replace" the whole
jspwiki.properties file, which may lead to problems when jspwiki evolves
and yet not existing options will be removed because thy're missing in
the overlay file.
Is there any option I can set to just change the path to
jspwiki-custom.properties?
Kind regards
Peter
