I got it working but do not know why it didn't work in the first place: If I substitute the home for pages from "/home/rsc/jspw" to "webapps/jspw/pages" and copy all the pages over JSPWiki works as usual.
Below tomcat6/conf (linked to /etc/tomcat6 on Debian) there is a file "context.xml". I changed the first line to <Context allowLinking="true">. However, this does not let me define a pages folder that is not physically located below /var/lib/tomcat6. Neither by linking from /var/lib/tomcat6/webapps/jspw/pages to /home/rsc/jspw nor by specifying /home/rsc/jspw directly in jspwiki.properties. While this seems to be nice security feature I'd like to know how this is achieved in tomcat6. Also I like to know how one can switch that rigid security off. allowLinking="true" doesn't help, at least not alone. May be I should ask on tomcat list? Rolf Rolf Schumacher wrote: > Dear JSPWiki Expert, > > with a new Debian system I firstly tried to install tomcat by "apt-get > install tomcat6". > > Than I "jar -xf JSPWiki.jar" to webapps/jspw. It's 2.8.3. > Edited jspwiki.properties, let the wiki files reside in /home/rsc/jspw > (see http://pastebin.ca/1841933). > Extracted the core pages to that directory, gave the directory itself a > 777 access code, all the files in there 666. > Restarted Tomcat and got this errors in catalina.out: > > http://pastebin.ca/1841932 > > Of course, I do not understand that messages. > > You know what's going on here? > > Rolf > >
