|
|
Apache Cocoon requires the following systems to be already installed in your system:
Java Virtual Machine
A Java 1.2 or later compatible virtual machine must be present for both
command line and servlet type usage of Apache Cocoon. Note that all servlet engines
require a JVM to run so if you are already using servlets you already have
one installed.
Servlet Engine
A Servlet 2.2 compliant servlet engine must be present in order to support
servlet operation and dynamic request handling. Note that this requirement
is optional for command line operation.
If you don't have a servlet engine installed, well, stop right here and
go to the Apache Tomcat project
http://jakarta.apache.org/tomcat/
then come back when you are done.
|
 |  |  |
 | Set JAVA_HOME environment variable |  |
 |  |  |
 |  |  |
 | Create the Cocoon WAR package |  |
 |  |  |
 |  |  |
 | Making the sql examples work out of the box |  |
 |  |  |
|
In most servlet engines, this is just a matter of copying
the war file in a specific directory and the engine will take
care of installing it when restarted.
Tomcat currently uses a different version of the XML parser
than Cocoon. To get Cocoon to work, you need to perform the
following steps:
-
Stop Tomcat
Go to the tomcat/bin directory, and run the shutdown script.
-
Delete tomcat/lib/jaxp.jar
Tomcat's jaxp.jar is 'sealed', and since xerces contains its
own implementation of the JAXP standard extension, Java
will fail to load xerces and report a 'Package Sealing Violation'
if both are in the classpath.
-
Rename tomcat/lib/parser.jar to tomcat/lib/zparser.jar
Tomcat's parser.jar contains older versions of some the same
XML APIS that Xerces uses, and these will prevent Xerces from
functioning properly if they appear before Xerces in the classpath.
Since Tomcat's startup scripts automatically load all the jar files
in tomcat/lib in name order, changing the name of the file causes it
to be loaded last in the classpath.
-
Copy cocoon/lib/xerces-XXX.jar file to tomcat\lib
Cocoon will now be able to see and use the correct XML libraries.
-
Copy cocoon/build/cocoon/cocoon.war into tomcat/webapps
-
Start Tomcat
Go to the tomcat/bin directory, and run the startup script.
-
Start using Cocoon
Access the URI
http://localhost:8080/cocoon/
with your favorite browser and start to enjoy the world of Cocoon.
Note that the first time you access Cocoon, it will take a few
seconds to start, since Cocoon needs to compile parts of itself.
|
Tomcat 4 is a really straight-forward installation.
-
Build the Cocoon webapp
Build the webapp as described above.
-
Copy cocoon/build/cocoon/cocoon.war into tomcat/webapps
-
Start Tomcat
Go to the tomcat/bin directory, and run the startup script.
-
Start using Cocoon
Access the URI
http://localhost:8080/cocoon/
with your favorite browser and start to enjoy the world of Cocoon.
Note that the first time you access Cocoon, it will take a few
seconds to start, since Cocoon needs to compile parts of itself.
|
 |  |  |
 | Installing on JBoss 2.2.2 with Tomcat 3.2.2 |  |
 |  |  |
 |  |  |
 | Installing on Resin 2.0.x |  |
 |  |  |
|
|
|