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.

Tomcat#


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:
java.lang.NullPointerException
at com.ecyrd.jspwiki.TemplateManager.findJSP(TemplateManager.java:155)
at com.ecyrd.jspwiki.tags.IncludeTag.doEndTag(IncludeTag.java:66)
at org.apache.jsp.wiki2.Wiki_jsp._jspService(Wiki_jsp.java:147)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
...


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 jspwiki.properties

--Manu

Jo#

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

WebLogic#

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

Resin#

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 -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

Jetty#

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#

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
txt
1Test.txt 40.6 kB 1 28-Nov-2007 05:57 204.254.175.249
policy
jspwiki.policy 2.9 kB 1 15-Feb-2006 20:45 198.102.62.250
« This particular version was published on 14-Jul-2006 18:48 by 199.43.48.87.