Twiki, if ported to J2EE would be much stronger as a CMS. The use of Java and XML should allow creating a client application for interfacing to sites that run Twiki. If not a client, the use of XMLRPC or SOAP to create a faster web based Twiki editing application would become possible.

Javadocs and published APIs for java will spur excellent Plugin development (Twiki already has excellent plugins and add-ons, but I think somehow it will benefit from Java).

It may be my love for Java that brought me here to post this request, but I hope other users can present strong arguments and justify the use of Java over perl/CGI enough so that someone can port Twiki to Java.

-- AnandChhatpar - 25 Mar 2003

This is a FAQ - please see Google:twiki+java+rewrite, but note that this is very unlikely to happen.

-- RichardDonkin - 25 Mar 2003

You might want to look at http://xwiki.org - their goals are aligned with yours.

-- MartinCleaver - 21 Dec 2004

The main win of porting TWiki to Java is the hold of state on the server side. That way, preferences and plugins won't need to be readed/initialized on EACH page view.

Besides that, there is no big gain and has a big "against": Java Web Containers are not that popular in both the intranets and in hosted enviroments.

-- RafaelAlvarez - 21 Dec 2004