Hi Juan,
I've not yet actively used Wildfly, too, but want to use it for learning
some JEE frameworks. And using JspWiki for my notes seemed to be somehow
"natural".
So I prefer a stable server without doing too much administration,
especially I don't want to change any startup scripts which are usually
managed by pacman (the package manager).
However, it's possible to add "system properties" (which are handled
like those provided by "-D..." to the java runtime) using the admin
console, so this perfectly fits when using "jspwiki.custom.config" property.
Kind regards
Peter
Am 12.02.19 um 14:53 schrieb Juan Pablo Santos Rodríguez:
Hi Peter,
you're absolutely right, I've just updated Getting Started and
Documentation pages to reflect all the possible ways
of specifying the jspwiki-custom.properties file location. Regarding 1. and
2, I misread your e-mail, what I wanted
to say is that the file could be readed if it is on server's classpath;
don't know wildfly in detail but surely has other
directories than the temporary ones that are on the server classpath.
In any case, the important bit is that the documentation was lacking and
hopefully is fixed now. Thanks for pointing
it out.
best regards,
juan pablo
On Tue, Feb 12, 2019 at 9:09 AM Peter Nabbefeld <peter.nabbef...@gmx.de>
wrote:
Hi Juan,
it seems You missed the point:
1. IMHO, it's not a good idea to put configuration files into a
temporary directory.
2. In a server environment (in my case JBoss Wildfly), configuration
files should be in some folder related to the server.
3. To achieve this, I needed a configuration option which is NOT
mentioned in the documentation: jspwiki.custom.config - this property
solves my problems, as I can set it from Wildfly configuration.
So, IMO, it would be a great idea, if somebody could add this to jspwiki
documentation.
Kind regards
Peter
Am 12.02.19 um 08:56 schrieb Juan Pablo Santos Rodríguez:
Hi Peter,
glad you were able to have JSPWiki running. We've got documented
jspwiki-custom.properties behaviour at
https://jspwiki-wiki.apache.org/Wiki.jsp?page=Documentation#section-Documentation-ConfigurationAndAdministration
which is linked from
https://jspwiki-wiki.apache.org/Wiki.jsp?page=Getting%20Started#section-Getting+Started-Configuration
(just added a small clarification there).
Also, by default, jspwiki only uses temp dir, as indicated by the
java.io.tmpdir property, to store lucene and ehcache related files, the
user dir for wiki pages and the server directory (logs will be placed
there).
HTH,
juan pablo
El mar., 12 feb. 2019 8:21, Peter Nabbefeld <peter.nabbef...@gmx.de>
escribió:
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
