jspwiki-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Harry Metske <harry.met...@gmail.com>
Subject Re: steps to get jspwiki-2.10.1-rc1 running with container managed aut
Date Mon, 26 May 2014 16:35:18 GMT
The way JSPWiki currently works is optimized for a setup where you have :
* one jspwiki instance in tomcat
* write access to tomcat's lib directory

If you miss one of these, you have to do something withing the exploded war
to get the properties file on the classpath.
In that case I would recommend to put the jspwiki-custom.properties in the
./webapp/JSPWiki/WEB-INF/classes folder. That way it is easy
visible/editable (as opposed to "hiding" it in the JSPWiki.jar). I just did
a minor correction on the wiki for that.

kind regards,
Harry



On 26 May 2014 16:29, Glen Mazza <glen.mazza@gmail.com> wrote:

> Hello Jürgen, while it will work, I recommend against placing the
> jspwiki-custom.properties file within the WAR.  Just place it in the Tomcat
> "lib" folder, and JSPWiki will automatically pick it up and use its values
> to override whatever is in jspwiki.properties.  (If you're inclined to
> place that file in the WAR you might as well directly edit the
> jspwiki.properties instead.)  This way you can upgrade the WAR as often as
> you want, and the values from the Tomcat lib custom.properties will
> automatically carry over.
>
> Also, remember your jspwiki-custom.properties file only has to have the
> (relatively few) values that you are overriding in jspwiki.properties, the
> latter's defaults will take over otherwise.
>
> I'll try to update our Wiki for this -- https://jspwiki-wiki.apache.
> org/Wiki.jsp?page=Documentation, right now for some reason I haven't
> write access.  :/
>
> Finally, in our JSPWiki source code we have an integrated test for CMA (
> http://svn.apache.org/viewvc/jspwiki/trunk/jspwiki-it-tests/), perhaps
> its settings there will be of help for you.
>
> Regards,
> Glen
>
>
>
> On 05/26/2014 05:24 AM, Jürgen Weber wrote:
>
>> My steps to get jspwiki-2.10.1-rc1 running with container managed auth:
>>
>> explode the war to /projekte/jspwiki-2.10.1-rc1/JSPWiki
>>
>> add
>> /projekte/apache-tomcat-8.0.8/conf/Catalina/localhost/JSPWiki.xml
>>
>> <Context path="/JSPWiki"
>> docBase="/projekte/jspwiki-2.10.1-rc1/JSPWiki">
>> </Context>
>>
>> change
>> /projekte/apache-tomcat-8.0.8/conf/server.xml
>>
>>    <role rolename="Authenticated"/>
>>    <role rolename="Admin"/>
>>
>>    <user username="tomcat" password="tomcat" roles="tomcat, Admin,
>> Authenticated"/>
>>
>> in web.xml enabled CONTAINER-MANAGED AUTHENTICATION & AUTHORIZATION
>>
>> and
>>
>> removed all annoying and useless (JSPWIKI-212):
>>         <user-data-constraint>
>>             <transport-guarantee>CONFIDENTIAL</transport-guarantee>
>>         </user-data-constraint>
>>
>>
>> There should be a
>>
>> jspwiki-custom.properties.template in the war.
>>
>> I used this for /projekte/apache-tomcat-8.0.8/
>> lib/jspwiki-custom.properties
>>
>> jspwiki.applicationName = JSPWiki
>> jspwiki.baseURL=http://linda:8080/JSPWiki
>> jspwiki.urlConstructor = ShortViewURLConstructor
>> jspwiki.pageProvider = VersioningFileProvider
>> jspwiki.fileSystemProvider.pageDir = /projekte/jspwiki-2.10.1-rc1/
>> wikipages
>> jspwiki.basicAttachmentProvider.storageDir =
>> /projekte/jspwiki-2.10.1-rc1/wikipages
>> #
>> log4j.appender.FileLog = org.apache.log4j.RollingFileAppender
>> log4j.appender.FileLog.MaxFileSize    = 10MB
>> log4j.appender.FileLog.MaxBackupIndex = 14
>> log4j.appender.FileLog.File = /projekte/jspwiki-2.10.1-rc1/jspwiki.log
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message