cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <stef...@apache.org>
Subject Re: More on Cocoon 2 Get going documentation.
Date Mon, 27 Mar 2000 10:59:25 GMT
Niclas Hedhman wrote:
> 
> Please find included minor revision of the installing.xml document to
> make Cocoon 2 work.

Hmmm

> Niclas
> 
>     ---------------------------------------------------------------
> 
> Cocoon requires the following systems to be already installed in your
> system:
> 
>    * Java Virtual Machine A Java 1.2 or greater compatible virtual
>      machine must be present for both command line and servlet type
>      usage of 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.x 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.
> 
> Cocoon is a publishing framework and was designed to be highly modular
> to allow users to choose their preferred implementation for the
> required component and to allow better and faster parallel
> development.
> 
> Previous releases of Cocoon forced you to download all the basic
> required packages for the installation, but this generated lots of
> problems for lack of synch between the projects and the complexity of
> the operation. For this reason, Cocoon now ships with all the required
> packages, a sort of a simple distribution to make things easier for
> you. We apologize for the increased size of the distribution, but we
> think this will be worthwhile even for users with low bandwidth.
> 
> In the /lib directory you'll find all the required packages. Now jump
> to the installation instructions for your servlet engine.
> 
> The Ant and Stylebook packages are only used in the build system and
> are not used by Cocoon at run-time. So you can safely ignore them in
> the installation.
> 
> Being Cocoon a servlet, you should be able to install it on every
> compliant servlet engine by associating the "org.apache.cocoon.Cocoon"
> servlet with the requests you want it to handle. In order to do this,
> there is no standard way, so we try to provide detailed information
> for the most used servlet systems.
> 
> First thing to do is to make sure that Cocoon and all the needed
> components (as explained in the previous section) are visible. This
> implies adding this to the servlet engine classpath by adding a bunch
> of classpath lines to your jserv.properties file for each jar package.
> 
> wrapper.classpath=[path-to-jar]/[jar-name].jar
> 
> Here is an example:
> 
> wrapper.classpath=/usr/local/java/jdk/lib/tools.jar
> wrapper.classpath=/usr/local/java/lib/cocoon.jar
> wrapper.classpath=/usr/local/java/lib/xerces.jar
> wrapper.classpath=/usr/local/java/lib/xalan.jar
> wrapper.classpath=/usr/local/java/lib/fop.jar ... from this version of
> Cocoon the cocoon.jar package should be added to the servlet engine
> classpath as any other required package (as shown above). JServ is a
> Servlet 2.0 compliant servlet engine and will not work if you place
> the Servlet_2.2.jar in its classpath. So ignore the servlet_2.2.jar
> package that is shipped with Cocoon if you use Jserv.
> 
> At this point, you must set the Cocoon configurations. To do this, you
> must choose the servlet zone(s) where you want Cocoon to reside. If
> you don't know what a servlet zone is, open the zone.properties file.
> 
> To configure Cocoon, you must pass the cocoon.properties file location
> to the servlet by adding the following line to the servlet zone:
> 
> servlet.org.apache.cocoon.servlet.CocoonServlet.initArgs=configurations=[path-to-cocoon]/conf/cocoon.xml
> 
> Note that you should not need to change anything from the template
> properties file found in the distribution (under /conf/), but you must
> edit it for more complex operation. Please refer directly to the file
> that contains breaf indications and comments on the different
> configurations, but you don't need to care about that at this point.
> 
> Now your cocoon servlet is properly configured, but you should tell
> Apache to direct any call to an XML file (or any other file you want
> Cocoon to process) to the Cocoon servlet. To do this, you should add
> the following line to your jserv.conf file:
> 
> Action cocoon /servlet/org.apache.cocoon.servlet.CocoonServlet
> AddHandler cocoon xml

No way man! What did we write the sitemap for?

This is _exactly_ the behavior that we are going to discouradge... and
part of the reason why you wanted to walk away from us.
 
> where xml is the file extention you want Cocoon to handle and
> /servlet/ is the mount point of your servlet zone (and the above is
> the standard name for servlet mapping for Apache JServ).
> 
> Restart both Apache and Apache JServ and try accessing the Cocoon
> status page:
> 
> http://localhost/Cocoon.xml
> 
> Cocoon will show you how it's configured.

No, this is not even implemented.
 
> If the page above is working, place the samples contained in the
> distribution (under ./samples) in your web server URI space and call
> index.xml to see Cocoon in action.
> 
> For any problem, please go to the FAQ list before submitting a bug
> report or a request for help on the mail lists. Thank you.

I'd better write some docs soon.

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<stefano@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------
 Missed us in Orlando? Make it up with ApacheCON Europe in London!
------------------------- http://ApacheCon.Com ---------------------



Mime
View raw message