This is version . It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

JSPWiki is developed and run on Tomcat 4.0 and above Servlet Container. For various reasons, someone might want to use alternative Java implementations. Please list your experiences here.


With Tomcat 5.0.28, I get an NPE which is caused by a null value passed to the setPage() method in the IncludeTag.
By watching the logs in detail, I get:

2006-06-24 21:44:40,683 http-8080-Processor24 DEBUG com.ecyrd.jspwiki.auth.AuthorizationManager JSPWiki:Main - Page defines no permissions for manuel, checking defaults.
2006-06-24 21:44:40,683 http-8080-Processor24 DEBUG com.ecyrd.jspwiki.auth.AuthorizationManager JSPWiki:Main - No defaults exist, falling back to hardcoded permissions.
2006-06-24 21:44:40,683 http-8080-Processor24 DEBUG com.ecyrd.jspwiki.auth.AuthorizationManager JSPWiki:Main - Permission ViewPermission for user UserProfile: 'manuel' is 1
2006-06-24 21:44:40,715 http-8080-Processor24 DEBUG com.ecyrd.jspwiki.WikiEngine JSPWiki:Main - Servlet path is: /Error.jsp
2006-06-24 21:44:40,715 http-8080-Processor24 DEBUG com.ecyrd.jspwiki.WikiEngine JSPWiki:Main - Mapped to nul l
2006-06-24 21:44:40,722 http-8080-Processor24 DEBUG JSPWiki JSPWiki:Main JSPWiki:Main - Error.jsp exceptio n is:
at com.ecyrd.jspwiki.TemplateManager.findJSP(
at com.ecyrd.jspwiki.tags.IncludeTag.doEndTag(
at org.apache.jsp.wiki2.Wiki_jsp._jspService(
at org.apache.jasper.runtime.HttpJspBase.service(
at javax.servlet.http.HttpServlet.service(
at org.apache.jasper.servlet.JspServletWrapper.service(
at org.apache.jasper.servlet.JspServlet.serviceJspFile(
at org.apache.jasper.servlet.JspServlet.service(
at javax.servlet.http.HttpServlet.service(
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(

Ok, I just found the root cause: it was in com.ecyrd.jspwiki.TemplateManager, the "DIRECTORY" was set to "templates" whereas my files are in a subdir called "wiki2". An improvement could be to have this kind of non-root paths configurable in



It works very good, versioning is working, too.
At the moment I have only a problem on attaching files.

Bea WebLogic#

I have it running on WLS, actually I also work for BEA incidentally. Let me know if there are any issues - Dain Hansen

Tag Error with 5.1, 6.1, and possibly others:

weblogic.servlet.jsp.JspException: (line 5): Error in using tag library uri='/WEB-INF/jspwiki.tld'
prefix='wiki': The Tag class 'com.ecyrd.jspwiki.tags.AttachmentsIteratorTag' has no setter method
corresponding to TLD declared attribute 'page', (JSP 1.1 spec, 5.4.1)

To fix add the setPage and getPage methods to com.ecyrd.jspwiki.tags.IteratorTag, which is the parent file, from one of the other tag source files like

Actually, the problem was that the attribute "page" in jspwiki.tld was extraneous (a cut-n-paste error). Fixed in 2.0.33.

-- JanneJalkanen

Sorry, but I'm still noticing this problem in 2.0.36 with AttachmentsIteratorTag, and also SearchResultIteratorTag, HistoryIteratorTag classes.

-- JeffPhillips

I must've been eating the wrong kind of mushrooms or something. It seems to be fixed in 2.1.x, but not in 2.0.x. The fix is really now in 2.0.41. I checked. Many times. A third release of the stable branch will be forthcoming. In the meanwhile, you can just remove the "page"-attribute totally from any conflicting TLD entries. For more information, see JSPWikiDownload.

-- JanneJalkanen

Unfortunately, this problem resurfaces in 2.1.115-alpha (on Weblogic 8.1). I solved it by adding four blank methods to

  • public void setPage( String page ) { }
  • public void setAttribute( String attr ) { }
  • public String getPage( ) { return null; }
  • public String getAttribute( ) { return null; }
I am not sure whether I could just delete the attributes from jspwiki.tld or not, but adding blank methods seems to have worked -- Search works.

-- MikeTikilyaynen

There is still an error in de jspwiki.tld file (seems to already exist from version 2.1.134 and probably earlier), I m using 2.1.160 now:
In the 'Content' tag there is an empty tag, between 'error' and 'edit' (around line 150), you have to remove it.
Tomcat seems to have no problems with it, WL has.
However, after removing this it worked on WL 8.1 but 6.1 still gave me the same error, I still can not figure out why.

-- MP, 07-04-2005

CamelCase Not Working Problem

WebLogic contains the JakartaOro package in it's default weblogic.jar. This older version may cause the TranslatorReader to not match any CamelCase patterns. Confirmed the "broken" versions of Oro are 2.0 and 2.0.1. Versions 2.0.2 to 2.0.7 appear to work properly.

The workaround is to pre-append the JSPWiki's oro.jar to the classpath before weblogic.jar in However, this may break other apps that depend on the other version of Oro.

-- JeffPhillips

IBM WebSphere#

It runs well on WebSphere Application Server V5.0. The Versioning File provider is working too. Have not tested file attachments yet.

--Joneses Sphere Training

--Lance Bader


Resin 2.1.6 (and 2.1.7, at least, perhaps other versions) cannot use UTF-8 encoding (for Chinese/Japanese/etc characters), unless you add the following on top of every JSP page:

<%@ page contentType="text/html; charset=utf8" %>

This is being tracked as bug #983 at the Resin website.

Unfortunately, we can't add that to the distribution, because if we do, then changing into ISO-8859-1 requires deleting that line. One possibility would be to move completely into UTF-8 in the distro.

(Thanks to Kaichao)

JSPWiki 2.2.33 and below works great with Resin 3.0.9 & 3.0.17. Unfortuantly at present the 2.3.x releases of JSPWiki don't work with Resin. It appears to ignore the policy files, even when supplied on the command line. This means that out of the box the Wiki always goes to the login screen.

-- RobertMcGovern

We've been trying to get Resin 3 working with the 2.3.x releases of JSPWiki and we are running into the same issue Robert ran into. With the security manager enabled <security-manager/> on the resin.conf, then doing httpd.exe"path_to_security_policy" - it reads the security policy file just fine, but simply ignores the SignedBy grants. (the keystore file is in the same location as the policy file) but doesn't have a problem enforcing other grants on the security policy file. I believe it's a problem with Resin 3's implementation of its classloader.

I've attached the security policy file we were using.

I tested JSPWiki 2.4.6 with resin 3.x and after some modifications , we could able to configure JAAS .

-- Kishore


Anyone able to get JSPWiki running on Jetty?

Yes, using jetty-5.1.6 and 5.1.10. Version 5.1.7 and later requires a symlink in <jetty_dir>/ext to log4j.jar of JSPWiki (or you may also copy log4j.jar into <jetty_dir>/ext).

-- Alexander, 26-01-2006; Updated 04-03-2006

Oracle Application Server#

It runs well on Oracle Application Server 10g (9.04). The Versioning File provider and attachments are working too.

--Lutz Tietze


Winstone is a free Java Servlet Container. I am running JSPWiki since version 2.0.52 on it.

--ElRey, 04.Mrz.06

Add new attachment

Only authorized users are allowed to upload new attachments.

List of attachments

Kind Attachment Name Size Version Date Modified Author Change note
1Test.txt 40.6 kB 1 28-Nov-2007 05:57
jspwiki.policy 2.9 kB 1 15-Feb-2006 20:45
« This particular version was published on 14-Jul-2006 16:48 by