Hosted on SourceForge

Mailing Lists

Files organisation
Going on inline

Java classes

> Installation

Java JDK

Chello requires a Java Development Kit. JDK 1.2 or later compatible must be installed.

Set the JAVA_HOME environment variable to point to the root directory of the Java Development Kit installed on your machine

[unix] JAVA_HOME=/path/to/java/

[win32] SET JAVA_HOME=c:\path\to\java

For Win32, the best is to set environment variables directly in the control panel

You also need to add JDK bin directory in your PATH


Chello requires Tomcat 3.x as a servlet engine. Download it from and install it in your system

Set the TOMCAT_HOME environment variable to point to the root directory of your Tomcat installation

[unix] TOMCAT_HOME=/path/to/tomcat/

[win32] SET TOMCAT_HOME=c:\path\to\tomcat

If you access Internet using a proxy server, it is wise to set TOMCAT_OPTS this way

[unix] TOMCAT_OPTS="-Dhttp.proxyhost=proxyserver -Dhttp.proxyport=proxyport"

[win32] SET TOMCAT_OPTS=-Dhttp.proxyhost=proxyserver -Dhttp.proxyport=proxyport

Patch Tomcat for Cocoon2:

  • Delete tomcat/lib/jaxp.jar
  • Rename tomcat/lib/parser.jar to tomcat/lib/zparser.jar
  • Copy chello/lib/xerces-XXX.jar file to tomcat\lib


Besides the required tools described above, you are strongly encouraged to download and install a source code control system, such as CVS, to maintain historical versions of the source files that make up your web application. Besides the server, you will also need appropriate client tools to check out source code files, and check in modified versions.

Detailed instructions for installing and using source code control applications is beyond the scope of this manual. However, CVS server and client tools for many platforms (along with documentation) can be downloaded


Although Chello includes a binary distribution of the Ant development tool, it does not include the Ant developer documentation. This can be accessed from


Chello uses JUnit for performing Unit Tests but it does not include the JUnit developer documentation

This can be accessed from


Chello uses HTTPUnit for performing Functional Tests but it does not include the HTTPUnit developer documentation

Refer to HTTPUnit documentation at


Cello uses XSLDOC for generating documentation for you XSL stylesheets. XSLDOC documentation can be accessed from

Cruise Control

Chello also includes Cruise Control, a tool for setting up a continuous build process.

Jikes Compiler

Chello allows you to use the fast Jikes compiler if you like. You can get it from

Chello Documentation