Cocoon is a web application which can be deployed on number of Java Servlet Engines. Here are some complements to the Official installation guide, which has lots of information on this subject.
See also CocoonEasyInstallation
If you just want to test Cocoon or play with the samples, see the INSTALL.txt file in the Cocoon distribution, or the How to run and explore the Cocoon samples page.
Additional installation information
Here are updates to this guide which did not make into the official guide yet.
"Could not create task or type of type: if." error: The cause of this error is use of a system-installed Ant instead of the one provided with Cocoon. The provided Ant defines the <if> task. Workaround: uninstall the system Ant. If you don't want to do that, you might try editing the tools/bin/ant script to force it to use Cocoon's Ant instead of the system one by setting no_config=true in the Extract launch and ant arguments (this works on SuSE 9.2). This error is known to occur on Linux (SuSE and Fedora) with Cocoon 184.108.40.206 and 2.1.6. (Reported by Lars Huttar; thanks to Antonio Gallardo for the fix.)
Linux Fedora Core 1, 2 or 3: Comes with own versions for java, javac, jar and optionally for ant. You need to remove the links placed in /usr/bin for this files. All these files are pointing to /etc/alternatives and from there point to /usr/share/java/libgcj-java*-placeholder.sh. Then read Cocoon2.1m2SetupLinuxredhat8.0
Linux Fedora Core 4: You need to add --noconfig before -logger to the ant command (line 41) in build.sh. You do not have to rename any Java or Ant executables. This works with /etc/alternatives just fine.
JBoss 3.01RC1 : Easy install, no customization necessary. Just drop cocoon.war into server/default/deploy directory. Thanks to Vegan Portal for information. This Information should be updated. With JDK1.4 it is still NOT running.
BuildSystem : an explanation of the Cocoon build system
- Cocoon 2.1m2 comes with a new build.xml file that only has the webapp target. That said, it is highly recommended that you read the Install.txt file in the Cocoon2.1m2 base directory. Jetty has become the new default servlet container and the way you get (or remove) optional components (blocks) has been changed.
Cocoon2.1DevSetupWin2000 : Cocoon 2.1 Dev instal for Dummies. Information how to setup Cocoon 2.1 Dev + Java SDK 1.4.1 + Tomcat 4.1.18 + on a Windows 2000 PC. - DEVELOPMENT VERSION
Cocoon2.1m2SetupLinuxredhat8.0 : Cocoon 2.1 m2 install for Dummies. Information how to setup Cocoon 2.1m2 + Java SDK 1.4.1_02 + Tomcat/4.1.24-LE-jdk14 + on a RedHat8.0 linux box. - DEVELOPMENT VERSION
CocoonDistSetupWin2000 : Cocoon 2.04 instal for Dummies. Information how to setup Cocoon 2.04 + Java SDK 1.3.1 + Tomcat 4.1.18 + on a Windows 2000 PC. - LAST RELEASE
IIS: someone mentions using the commercial isapirewrite DLL (www.isapirewrite.com), to connect Cocoon to the IIS server. And no, we dont' hate this. Isapirewrite writes the original URL in the IIS logfiles, instead of the 'rewritten' one. This solves the issue with the jakarta redirect DLL which floods your log with 'jakarta_redirect.dll' hits.
Cocoon 2.1 CVS 20030421 on WebLogic 8.1 quick install steps (assume Win platform and WebLogic installed under C:\Bea):
Have fresh WebLogic 8.1 install (no changes to endorsed and other lib folders)
- set JAVA_HOME=C:\Bea\jdk141_02
Edit root sitemap.xmap, change <map:match pattern=""> to <map:match pattern="welcome">
- Build Cocoon from fresh checkout by typing build.bat
- Copy cocoon-2.1\build\webapp folder into
C:\Bea\WebLogic8.1\samples\domains\examples\applications, rename folder to "cocoon"
That's it. Step 3 (sitemap edit) is because there's some evil redirection going on to index.html...