I fail to see why this is jspwiki-custom.properties harder for multiples?
What would you propose?
--
-jim
Jim Willeke
On Fri, Jun 1, 2018 at 7:21 AM, Foster Schucker wrote:
> So it's a chicken and egg. We can make it harder for the multiples to
> work and make it easier for the singles.
>
> I
So it's a chicken and egg. We can make it harder for the multiples to
work and make it easier for the singles.
I'm worried about making it impossible for the multiples to work. I'm
one of the multiples, and having the setup the way it is is super simple
for me.
Maybe one of the maintainers
One major advantage of the user-properties file is that its settings (eg
location of your page repository, ...) are retained when deploying a new
version of jspwiki war.
dirk
On Thu, May 31, 2018 at 3:00 PM Paul Uszak wrote:
> Are you convinced that this is the typical use case that you
Are you convinced that this is the typical use case that you want to
target? The percentage of multiple jspwikis must hover around 1%. Look at
it from the perspective of the mainstream user base. IMHO, this unnecessary
flexibility is actually a major obstacle to installation and usability.
Cutting
if I remember correctly, the most important reason was that it allows you
to configure multiple jspwiki’s running in the same appserver.
Since java system properties (-D) are jvm wide you can t do it with that.
And setting system properties in moat hosted jvms are not allowed.
We could of course a
Any reason that this isn't done the traditional way with a -D system
property pointing to an external .properties file? That way you'd only have
one file and be able to see all the configuration parameters should you
wish to change some... Large applications (including Tomcat itself) are
configured
That did it! Thanks a lot!
On Wed, May 30, 2018 at 3:32 PM, Harry Metske
wrote:
> setting custom properties should be done with the jspwiki-custom.properties
> file.
> See
> https://jspwiki-wiki.apache.org/Wiki.jsp?page=Documentation#section-
> Documentation-ConfigurationAndAdministration
>
> h
setting custom properties should be done with the jspwiki-custom.properties
file.
See
https://jspwiki-wiki.apache.org/Wiki.jsp?page=Documentation#section-Documentation-ConfigurationAndAdministration
hope that helps
regards,
Harry
Op wo 30 mei 2018 om 22:18 schreef Blake McBride
> Thanks for t
Thanks for the help, but I am confused. Tomcat explodes the war into the
app directory. It doesn't explode any jar files within a war. What good
is it in the jar? How can I edit it? Do I extract it, edit it, re-jar
it? Is jspwiki.war a tomcat redy-to-go web app?
Thanks!
Blake
On Wed, May
the jspwiki properties file is inside the jspwiki.jar which is in the
jspwiki.war.
So you have to recurse one level deeper :-)
cheers,
Harry
Op wo 30 mei 2018 om 21:33 schreef Blake McBride
> Hi.
>
> The page at https://jspwiki-wiki.apache.org/Wiki.jsp?page=Configuration
> states:
>
> "This is
Hi.
The page at https://jspwiki-wiki.apache.org/Wiki.jsp?page=Configuration
states:
"This is simple dump of the *jspwiki.properties *file contained in
JSPWiki.war."
I downloaded JSPWiki.war from
http://mirror.metrocast.net/apache/jspwiki/2.10.4/binaries/webapp/JSPWiki.war
I then type: jar tvf
11 matches
Mail list logo
