






































|
I followed the standard Cocoon install instructions but without success. (Most of it is
there but it could be a bit clearer.)
I have listed below the key steps that actually got the combination shown
above to work.
I have included sections on installing Java SDK, Apache and Jakarta-Tomcat to avoid
any possible ambiguity. So, there may be more detail than is actually required - but
why not - as long as it all works in the end !
The relevant sections of the modified files mentioned have been partially listed.
The steps listed below mention my own machine name and my own specific paths. Substitute
your own naturally. I thought it was better to leave them in to avoid the "path to your..."
directives which can sometimes be ambiguous when it comes to how paths are specified within
the Windows environment i.e forward ("/") and backward slashes ("\") etc ..
 |
Warning : This is long and verbose ! The steps and file listings should be read in the order given i.e top
down to bottom.
|
 |
Before I started this setup on my machine, I did not have any pre-existing
Java SDK, Apache Web Server, Jakarta-Tomcat, Cocoon, or even anything in the
CLASSPATH env variable. It was a completely new install on a fresh Windows
2000 Professional machine.
|
OK lets go....
|
- Install Sun Java SDK SE V1.3 via the standard install procedure i.e execute the
.exe file.
- I chose to install at path
C:\Program_Files\jdk1.3 - Note the underscore in Program_Files .
- No worries !
|
 |  |  |  | Apache V1.3.12 HTTP Server |  |  |  |  |
- Install Cocoon via the standard install procedure.
- I chose to install (i.e unpack the zip) at path
C:\Program_Files\cocoon-1.7.4 - Note
the underscore in Program_Files. (Actually the important files in the Cocoon
distribution all end up being copied into the working Jakarta-Tomcat directories, so the unzipped
Cocoon can be either deleted or left where it is after the files have been copied.)
- Copy the
xerces_1_0_3.jar , xalan_1_0_1.jar , fop_0_12_1.jar and servlet_2_2.jar
files, found in the C:\Program_Files\cocoon-1.7.4\lib to the
C:\Program_Files\jakarta-tomcat\lib directory.
- Copy the
C:\Program_Files\cocoon-1.7.4\bin\cocoon.jar file to the
C:\Program_Files\jakarta-tomcat\lib directory.
- Modify
C:\Program_Files\jakarta-tomcat\bin\tomcat.bat to add the five Cocoon .jar
files to the Jakarta-Tomcat CLASSPATH env variable. See code segment below.
- Note the "
remed " out set CLASSPATH=%CLASSPATH%;%TOMCAT_HOME%\lib\servlet.jar line.
- Modify the
C:\Program_Files\jakarta-tomcat\conf\web.xml file to add the Cocoon
specific configuration directives. See code segment below.
- And now for the really really important step, copy the
C:\Program_Files\cocoon-1.7.4\conf\cocoon.properties file to the
C:\Program_Files\jakarta-tomcat\webapps\ROOT directory.
- Now, if everything has been performed as specified above and if the gods
are smiling on you today, then (and you'll hate me if it doesn't) it should
all work now.
- OK. To test it all, do the following :
- If Jakarta-Tomcat is still running, then kill it by typing
tomcat stop in a
Windows 2000 Command Prompt window which has been cded to C:\Program_Files\jakarta-tomcat\bin .
- If Apache is still running, then kill it by menu selecting
Action|Stop
through the Windows 2000 Services program.
- Now, start up Jakarta-Tomcat as detailed in the Jakarta-Tomcat V3.1 section shown above.
- Now, start up Apache as detailed in the Apache V1.3.12 HTTP Server section shown above.
- Start Internet Explorer.
- The big test - try and access
http://shaggy.blimp.au:8080/Cocoon.xml - You
should see the Cocoon V1.7.4 status page containing all of the internal configuration
information and settings specific to Cocoon. Note the 8080 port number.
- Note the uppercase "
C " in Cocoon.xml . Also, you won't find this file on the
hard disk, it is an internal page and its name is set in the cocoon.properties
file.
- OK, if the internal Cocoon status page is working then you can try and access the
Cocoon examples as follows :
- Copy the
C:\Program_Files\cocoon-1.7.4\samples directory to the
C:\Program_Files\jakarta-tomcat\webapps directory.
- Copy the
cocoon.properties file to the new C:\Program_Files\jakarta-tomcat\webapps\samples
directory - again this is a really important step.
- Kill Jakarta-Tomcat.
- Kill Apache.
- Restart Jakarta-Tomcat.
- Restart Apache.
- Try and access
http://shaggy.blimp.au:8080/samples/index.xml . Note the 8080 port number.
- You should see the Cocoon samples page.
- Thats it.
- Again, note that no files were copied into the
C:\Program_Files\Apache Group\Apache\htdocs
directory. The Cocoon samples are found via Jakarta-Tomcat and port 8080 .
- One last thing to try. Create a directory called
C:\Program_Files\jakarta-tomcat\webapps\gogo .
- Copy the Cocoon
hello-page.xml and hello-page-html.xsl files found in the
C:\Program_Files\cocoon-1.7.4\samples\hello directory into the new gogo directory.
- And again the really important step, copy the
cocoon.properties file into the
new gogo directory.
- Kill Jakarta-Tomcat.
- Kill Apache.
- Restart Jakarta-Tomcat.
- Restart Apache.
- Start Internet Explorer.
- Try and access
http://shaggy.blimp.au:8080/gogo/hello.xml .
- You should see the Hello Page.
- The purpose of the last few steps was to show how a new auto context can be
setup in the Jakarta-Tomcat
webapps directory.
As I see it, put your own custom XML/XSL files in a directory that lives within the Jakarta-Tomcat
webapps directory. Make sure cocoon.properites is also in there.
- You could also put your custom XML/XSL work into just the Jakarta-Tomcat
webapps/ROOT directory and
as long as cocoon.properties is also in there (which it should be or else you won't be able
to see the internal Cocoon.xml status page) then it should all work from that ROOT directory.
- In order to avoid Jakarta-Tomcat having to serve up everything on port
8080 , the
C:\Program_Files\jakarta-tomcat\conf\tomcat-apache.conf file can be modified by adding
the lines "AddType text/xml .xml " and "AddHandler jserv-servlet .xml ". (Refer to the start of the listing for
C:\Program_Files\jakarta-tomcat\conf\tomcat-apache-cocoon.conf below to see where the line should be.)
- After starting/stopping Jakarta-Tomcat and Apache in the same manner as described above you should now
be able to access XML files without specifying port
8080 . e.g http://shaggy.blimp.au/samples/index.xml .
Note : If your browser cannot find the file then make sure your C:\Program_Files\jakarta-tomcat\conf\server.xml
file has alias directives for the samples directory or follow the procedure in the next few steps.
- Note : You must be careful when making modifications to
C:\Program_Files\jakarta-tomcat\conf\tomcat-apache.conf
because this file is automatically generated each time Jakarta-Tomcat starts and will therefore overwrite any
modifications you have made. To complicate matters, the contents of C:\Program_Files\jakarta-tomcat\conf\server.xml ,
where you might specify some context "AutoSetup actions", determines some of the content of
C:\Program_Files\jakarta-tomcat\conf\tomcat-apache.conf , so simply making a once off copy of
C:\Program_Files\jakarta-tomcat\conf\tomcat-apache.conf and adding the "AddHandler jserv-servlet .xml "
line and referencing the copied .conf file with the include statement in
C:\Program_Files\Apache Group\Apache\conf\httpd.conf may also lead to problems.
- My solution was to eliminate all context AutoSetup actions in
C:\Program_Files\jakarta-tomcat\conf\server.xml , then copy
a freshly generated version of C:\Program_Files\jakarta-tomcat\conf\tomcat-apache.conf to C:\Program_Files\jakarta-tomcat\conf\tomcat-apache-cocoon.conf , then
add the line "AddHandler jserv-servlet .xml " to C:\Program_Files\jakarta-tomcat\conf\tomcat-apache-cocoon.conf , then
modify the include statement in C:\Program_Files\Apache Group\Apache\conf\httpd.conf to read
"include C:/Program_Files/jakarta-tomcat/conf/tomcat-apache-cocoon.conf ". This method places the onus on the webmaster
to make sure the copied and modified version of C:\Program_Files\jakarta-tomcat\conf\tomcat-apache-cocoon.conf is always
up to date. See code segment below.
- I have listed my simplified
C:\Program_Files\jakarta-tomcat\conf\server.xml file. Note the references to my test gogo
directory in file C:\Program_Files\jakarta-tomcat\conf\tomcat-apache-cocoon.conf which are needed in order to get the
hello-page.xml example working without using port 8080 in the address. See code segment below.
- Well, thats how I got it to work.
- Works for me and I hope for you too.
- Sorry for all the completely specfied file and directory paths, but it should at least be unambiguous. No worries !
C:\Program_Files\jakarta-tomcat\bin\tomcat.bat
 |  |  |  |
.................
set cp=%CLASSPATH%
set CLASSPATH=.
set CLASSPATH=%TOMCAT_HOME%\classes
set CLASSPATH=%CLASSPATH%;%TOMCAT_HOME%\lib\xerces_1_0_3.jar
set CLASSPATH=%CLASSPATH%;%TOMCAT_HOME%\lib\xalan_1_0_1.jar
set CLASSPATH=%CLASSPATH%;%TOMCAT_HOME%\lib\fop_0_12_1.jar
set CLASSPATH=%CLASSPATH%;%TOMCAT_HOME%\lib\servlet_2_2.jar
set CLASSPATH=%CLASSPATH%;%TOMCAT_HOME%\lib\cocoon.jar
set CLASSPATH=%CLASSPATH%;%TOMCAT_HOME%\lib\webserver.jar
set CLASSPATH=%CLASSPATH%;%TOMCAT_HOME%\lib\jasper.jar
set CLASSPATH=%CLASSPATH%;%TOMCAT_HOME%\lib\xml.jar
rem set CLASSPATH=%CLASSPATH%;%TOMCAT_HOME%\lib\servlet.jar
set CLASSPATH=%CLASSPATH%;%JAVA_HOME%\lib\tools.jar
.................
|  |  |  |  |
C:\Program_Files\jakarta-tomcat\conf\web.xml
 |  |  |  |
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
"http://java.sun.com/j2ee/dtds/web-app_2.2.dtd">
<web-app>
<servlet>
<servlet-name>
default
</servlet-name>
<servlet-class>
org.apache.tomcat.servlets.DefaultServlet
</servlet-class>
<load-on-startup>
-2147483646
</load-on-startup>
</servlet>
<servlet>
<servlet-name>
invoker
</servlet-name>
<!--
org.apache.tomcat.servlets.NoInvokerServlet
-->
<servlet-class>
org.apache.tomcat.servlets.InvokerServlet
</servlet-class>
</servlet>
<servlet>
<servlet-name>
jsp
</servlet-name>
<servlet-class>
org.apache.jasper.runtime.JspServlet
</servlet-class>
<!-- uncomment the following to use Jikes for JSP compilation
<init-param>
<param-name>jspCompilerPlugin</param-name>
<param-value>org.apache.jasper.compiler.JikesJavaCompiler</param-value>
</init-param>
-->
<load-on-startup>
-2147483646
</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>
invoker
</servlet-name>
<url-pattern>
/servlet/*
</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>
jsp
</servlet-name>
<url-pattern>
*.jsp
</url-pattern>
</servlet-mapping>
<session-config>
<session-timeout>
30
</session-timeout>
</session-config>
<!-- Start Cocoon Section -->
<servlet>
<servlet-name>org.apache.cocoon.Cocoon</servlet-name>
<servlet-class>org.apache.cocoon.Cocoon</servlet-class>
<init-param>
<param-name>properties</param-name>
<param-value>
cocoon.properties
</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>org.apache.cocoon.Cocoon</servlet-name>
<url-pattern>*.xml</url-pattern>
</servlet-mapping>
<!-- End Cocoon Section -->
<mime-mapping>
<extension>
txt
</extension>
<mime-type>
text/plain
</mime-type>
</mime-mapping>
..........
|  |  |  |  |
C:\Program_Files\jakarta-tomcat\conf\tomcat-apache-cocoon.conf
 |  |  |  |
LoadModule jserv_module modules/ApacheModuleJServ.dll
ApJServManual on
ApJServDefaultProtocol ajpv12
ApJServSecretKey DISABLED
ApJServMountCopy on
ApJServLogLevel notice
ApJServDefaultPort 8007
AddType text/xml .xml
AddHandler jserv-servlet .xml
AddType test/jsp .jsp
AddHandler jserv-servlet .jsp
Alias /examples C:\Program_Files\jakarta-tomcat\webapps\examples
<Directory "C:\Program_Files\jakarta-tomcat\webapps\examples">
Options Indexes FollowSymLinks
</Directory>
ApJServMount /examples/servlet /examples
<Location /examples/WEB-INF/ >
AllowOverride None
deny from all
</Location>
Alias /test C:\Program_Files\jakarta-tomcat\webapps\test
<Directory "C:\Program_Files\jakarta-tomcat\webapps\test">
Options Indexes FollowSymLinks
</Directory>
ApJServMount /test/servlet /test
<Location /test/WEB-INF/ >
AllowOverride None
deny from all
</Location>
Alias /admin C:\Program_Files\jakarta-tomcat\webapps\admin
<Directory "C:\Program_Files\jakarta-tomcat\webapps\admin">
Options Indexes FollowSymLinks
</Directory>
ApJServMount /admin/servlet /admin
<Location /admin/WEB-INF/ >
AllowOverride None
deny from all
</Location>
Alias /samples C:\Program_Files\jakarta-tomcat\webapps\samples
<Directory "C:\Program_Files\jakarta-tomcat\webapps\samples">
Options Indexes FollowSymLinks
</Directory>
ApJServMount /samples/servlet /samples
<Location /samples/WEB-INF/ >
AllowOverride None
deny from all
</Location>
Alias /gogo C:\Program_Files\jakarta-tomcat\webapps\gogo
<Directory "C:\Program_Files\jakarta-tomcat\webapps\gogo">
Options Indexes FollowSymLinks
</Directory>
ApJServMount /gogo/servlet /gogo
<Location /gogo/WEB-INF/ >
AllowOverride None
deny from all
</Location>
ApJServMount /servlet /ROOT
|  |  |  |  |
C:\Program_Files\jakarta-tomcat\conf\server.xml
 |  |  |  |
<?xml version="1.0" encoding="ISO-8859-1"?>
<Server>
<!-- Debug low-level events in XmlMapper startup -->
<xmlmapper:debug level="0" />
<!-- This is quite flexible; we can either have a log file per
module in Tomcat (example: ContextManager) or we can have
one for Servlets and one for Jasper, or we can just have
one tomcat.log for both Servlet and Jasper.
If you omit "path" there, then stderr should be used.
verbosityLevel values can be:
FATAL
ERROR
WARNING
INFORMATION
DEBUG
-->
<Logger name="tc_log"
path="logs/tomcat.log"
customOutput="yes" />
<Logger name="servlet_log"
path="logs/servlet.log"
customOutput="yes" />
<Logger name="JASPER_LOG"
path="logs/jasper.log"
verbosityLevel = "INFORMATION" />
<!-- Add "home" attribute if you want tomcat to be based on a
different directory
"home" is used to create work and to read webapps, but not
for libs or CLASSPATH.
Note that TOMCAT_HOME is where tomcat is installed, while
ContextManager home is the
base directory for contexts, webapps/ and work/
-->
<ContextManager debug="0" workDir="work" >
<!-- ContextInterceptor className="org.apache.tomcat.context.LogEvents" / -->
<ContextInterceptor className="org.apache.tomcat.context.AutoSetup" />
<ContextInterceptor className="org.apache.tomcat.context.DefaultCMSetter" />
<ContextInterceptor className="org.apache.tomcat.context.WorkDirInterceptor" />
<ContextInterceptor className="org.apache.tomcat.context.WebXmlReader" />
<ContextInterceptor className="org.apache.tomcat.context.LoadOnStartupInterceptor" />
<!-- Request processing -->
<RequestInterceptor className="org.apache.tomcat.request.SimpleMapper"
debug="0" />
<RequestInterceptor className="org.apache.tomcat.request.SessionInterceptor" />
<RequestInterceptor className="org.apache.tomcat.request.SecurityCheck" />
<RequestInterceptor className="org.apache.tomcat.request.FixHeaders" />
<Connector className="org.apache.tomcat.service.SimpleTcpConnector">
<Parameter name="handler"
value="org.apache.tomcat.service.http.HttpConnectionHandler"/>
<Parameter name="port" value="8080"/>
</Connector>
<Connector className="org.apache.tomcat.service.SimpleTcpConnector">
<Parameter name="handler"
value="org.apache.tomcat.service.connector.Ajp12ConnectionHandler"/>
<Parameter name="port" value="8007"/>
</Connector>
</ContextManager>
</Server>
|  |  |  |  |
C:\Program_Files\Apache Group\Apache\conf\httpd.conf
 |  |  |  |
...........
#
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container.
#
#<VirtualHost ip.address.of.host.some_domain.com>
# ServerAdmin webmaster@host.some_domain.com
# DocumentRoot /www/docs/host.some_domain.com
# ServerName host.some_domain.com
# ErrorLog logs/host.some_domain.com-error_log
# CustomLog logs/host.some_domain.com-access_log common
#</VirtualHost>
#<VirtualHost _default_:*>
#</VirtualHost>
include C:/Program_Files/jakarta-tomcat/conf/tomcat-apache-cocoon.conf
|  |  |  |  |
|
|
|