I could solve this issue using a system property:
<property name="jspwiki.custom.config"
value="/opt/wildfly/appclient/configuration/jspwiki/jspwiki.properties"/>
However, I couldn't find this property in the documents (it may be
hidden somewhere, but I didn't see anything on the Configuration page,
where I'd expect it). I only "accidently" found it in the server logs
("No jspwiki.custom.config defined for this context"). Please, add a
note about this property so others will be able to find it!
Kind regards
Peter
Am 11.02.19 um 23:24 schrieb Peter Nabbefeld:
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
