You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jspwiki.apache.org by Jürgen Weber <ju...@jwi.de> on 2014/05/26 11:24:38 UTC
steps to get jspwiki-2.10.1-rc1 running with container managed aut
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
Re: steps to get jspwiki-2.10.1-rc1 running with container managed aut
Posted by Juan Pablo Santos Rodríguez <ju...@gmail.com>.
Hi,
maybe it's an overkill for home usage, but you can make use of maven's
overlays to generate a new war with your desired web.xml configuration and
other customizations, without having to open and modify JSPWiki war. That
way you could also put your configuration under version control / ci, and
updating the jspwiki version would be as easy as changing the jspwiki-war
dependency version, except in the case of a web.xml modification. All the
war modules inside the jspwiki-it-tests use this technique to build
specific custom war
br,
juan pablo
On Mon, May 26, 2014 at 9:09 PM, Jürgen Weber <ju...@jwi.de> wrote:
> I like the war and the separate jspwiki-custom.properties out of the war in
> Tomcat's lib, problem is that I alway use container auth and therefore have
> to explode the war to edit the web.xml
>
>
>
> 2014-05-26 18:35 GMT+02:00 Harry Metske <ha...@gmail.com>:
>
> > 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 <gl...@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
> > >>
> > >>
> > >
> >
>
Re: steps to get jspwiki-2.10.1-rc1 running with container managed aut
Posted by Jürgen Weber <ju...@jwi.de>.
I like the war and the separate jspwiki-custom.properties out of the war in
Tomcat's lib, problem is that I alway use container auth and therefore have
to explode the war to edit the web.xml
2014-05-26 18:35 GMT+02:00 Harry Metske <ha...@gmail.com>:
> 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 <gl...@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
> >>
> >>
> >
>
Re: steps to get jspwiki-2.10.1-rc1 running with container managed
aut
Posted by Glen Mazza <gl...@gmail.com>.
(umlaut in name = get to practice my high school German :) Ich habe
unsere Doku aktuelisiert:
https://jspwiki-wiki.apache.org/Wiki.jsp?page=Documentation
quote:
The default jspwiki.properties can be easilyviewed online
<http://svn.apache.org/viewvc/jspwiki/trunk/jspwiki-war/src/main/resources/ini/jspwiki.properties?view=co>from
our source code repository, note that version though points to the
"trunk" (latest code) which may differ a bit the JSPWiki release you are
using -- inspecting this file directly from within the WAR (open the WAR
with a file decompression tool and in the WEB-INF/lib folder, open the
JSPWiki*.jar file and look in the ini folder) will give you the actual
version you're using.
Cheers,
Glen
On 05/26/2014 02:46 PM, Jürgen Weber wrote:
> Glen, I had put jspwiki-custom.properties into
> /projekte/apache-tomcat-8.0.8/lib
>
> It's just that there is no properties whatever in the war, and I would have
> like a properties template in the war to work on.
>
> Juergen
>
>
> 2014-05-26 18:35 GMT+02:00 Harry Metske <ha...@gmail.com>:
>
>> 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 <gl...@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
>>>>
>>>>
Re: steps to get jspwiki-2.10.1-rc1 running with container managed aut
Posted by Jürgen Weber <ju...@jwi.de>.
Glen, I had put jspwiki-custom.properties into
/projekte/apache-tomcat-8.0.8/lib
It's just that there is no properties whatever in the war, and I would have
like a properties template in the war to work on.
Juergen
2014-05-26 18:35 GMT+02:00 Harry Metske <ha...@gmail.com>:
> 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 <gl...@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
> >>
> >>
> >
>
Re: steps to get jspwiki-2.10.1-rc1 running with container managed aut
Posted by Harry Metske <ha...@gmail.com>.
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 <gl...@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
>>
>>
>
Re: steps to get jspwiki-2.10.1-rc1 running with container managed
aut
Posted by Glen Mazza <gl...@gmail.com>.
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
>