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.

[{TableOfContents }]

! [Tomcat | http://jakarta.apache.org/tomcat/]

JSPWiki is developed on Tomcat, so all versions since 4.0 should work.


There are some issues on the 2.4 series, pre-2.4.51 on WebLogic 9, so please upgrade.

! [IBM WebSphere | http://www.ibm.com/websphere]

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


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|http://www.caucho.com/quercus/bugtrack/view.xtp?bugreport_id=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 -Djava.security.policy="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__

This bug is being tracked on Resin, as [bug id #1008|http://bugs.caucho.com/view.php?id=1008].  A fix is to be expected soon for Resin 3.


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|http://www.oracle.com/appserver/index.html]

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

--[Lutz Tietze|mailto://lutz.tietze@tietzenet.de]


[Winstone|http://winstone.sourceforge.net] is a free Java Servlet Container. I am running JSPWiki since version 2.0.52 on it.

--[ElRey], 04.Mrz.06