Forgive me, I'm assuming you have read the INSTALL.TXT in the
2.1.10distrubition. For convenience I enclose it here
+-----------------------------+
| I N S T A L L |
+-----------------------------+
Let me guess: you don't like to read verbose docs, right?
Great, this file is for you.
1) Unpack the distribution
Obviously you've done this already, but if you got errors when unpacking
the archive with tar, you might need to use gnutar instead. Our archives
contain long paths and filenames which cause problems with some versions
of the tar command.
2) Set your JAVA_HOME environment
You have to set your JAVA_HOME environment to point to the root directory
of
the Java Virtual Machine (JDK 1.3.x or later) installed on your machine.
To do this simply type:
[unix] JAVA_HOME=/path/to/java/
[win32] SET JAVA_HOME=c:\path\to\java
your mileage may vary depending on your shell, but you know how to setup
environments, right?
If you're using JDK 1.3.x, you have to exclude the JCR block before
building
Cocoon. Have a look at the "Choosing the blocks" section below on how to
exculude a block. Please note that some samples require JDK 1.4 or above.
3) Build Cocoon by typing "build" or "./build.sh"
4) Run Cocoon by typing "cocoon" or "./cocoon.sh"
5) Open http://localhost:8888/ with your browser
That's it!
Now, you have two choices:
a) close this file and try to hack something out by yourself
b) keep reading
Go ahead and choose option a), but don't complain if you can't figure out
how
to use the cocoon build system for your needs.
Still here? good. You won't regret it.
Updating
--------
If you are updating from a previous release of Cocoon, make sure
that you read the installation instructions on updating first.
Choosing the blocks
-------------------
Cocoon is composed by its 'core' and several 'blocks'.
The core (a.k.a. naked cocoon') contains the system with services that
are needed to all cocoon users. Blocks provide services that you might not
need,
therefore the build system allows you to remove them from the build.
Now, do the following steps to configure the blocks you want in your cocoon:
1) cp blocks.properties local.blocks.properties
2) edit local.blocks.properties
3) rebuild (do a "build clean" first if you deactivated some blocks)
do not modify blocks.properties directly!
Tuning the build
----------------
Ok, now that you told the build system what services you want assembled
into your distribution, you can tune the build for your personal needs:
1) cp build.properties local.build.properties
2) edit local.build.properties
do not modify build.properties directly!
An example of a local.build.properties is the following:
compiler=jikes
compiler.debug=off
build.webapp=/path/to/where/to/build/the/webapp
where you override default compilation parameters and tell the build system
where to place the generated cocoon webapp. Look into build.properties to
find
out what you might want to modify for your own personal needs.
Running Cocoon as a servlet
---------------------------
When you do 'cocoon servlet', the servlet container (jetty) is started and
Cocoon
loaded into it. By default, this is attached to port 8888, but you can
change
this by setting the "JETTY_PORT" environment property before launching
cocoon.
Other properties that you can change are:
JETTY_ADMIN_PORT (defaults to 8889): is the port where the jetty web
administration is connected to. This is available when you launch
"cocoon servlet-admin", otherwise its disabled.
JETTY_WEBAPP (defaults to build/webapp): is the location of the webapp
that jetty has to execute. modify this to match your
local.build.properties
if you modified where the build system creates your webapp
JAVA_DEBUG_PORT (defaults to 8000): is the port where the JVM over-the-wire
debug interface connects to. This is available only if you launch
"cocoon servlet-debug", otherwise is disabled. This is used by remote
debuggers (for example, Eclipse's).
Note that the "standalone-demo" build target prepares a directory that you
can
move elsewhere to run "cocoon servlet" outside of the build tree.
All right, that's it for now.
Happy hacking with Cocoon.
On 17/11/2007, Mansour <[EMAIL PROTECTED]> wrote:
>
> I 've had a look at this page before posting. However, I still need to
> know how things work (the servlet, web.xml, cocoon.xconf,...etc). I need
> to know how to wrap a web application in a war and throw it in the
> tomcat/webapp. Before, I learn how to use blocks I need to be able to
> write a small siplme application and build on top of it.
>
> If you know how to get this done, then please share the knowledge.
> Thank you.
>
> warrell harries wrote:
> > Hi,
> >
> > Have you followed the threads in the 2.10 release e.g.
> > http://cocoon.apache.org/2.1/howto/howto-explore-samples.html
> >
> > One of the advantages of Cocoon is that you do not need to get
> > involved in the Cocon servlet e.g. web.xml or the conventional
> > configuration e.g. cocoon.xconf. You only need concern yourself with
> > your 'block' sitemap. Have a look at a simple sample e.g. the Hello
> > World example or the request Generator and you will have an ah-ha
> moment.
> >
> > Please put in the effort and you will be rewarded ;-)
> >
> > On 17/11/2007, *Mansour* <[EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>> wrote:
> >
> > I am trying to write the simplest application using cocoon. Couldn't
> > find any tutorial. I would like to know what are the minimum
> > parameters
> > to go in the web.xml. All I need is a simple Hello World. Here's
> > what I
> > have so far:
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> > <web-app xmlns=" http://java.sun.com/xml/ns/j2ee";
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> > xsi:schemaLocation=" http://java.sun.com/xml/ns/j2ee
> > http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd";
> > version="2.4">
> >
> > <servlet>
> > <servlet-name> CocoonServlet </servlet-name>
> > <servlet-class> org.apache.cocoon.servlet.CocoonServlet
> > </servlet-class>
> > <init-param>
> > <param-name>configurations</param-name>
> > <param-value>/WEB-INF/cocoon.xconf</param-value>
> > </init-param>
> > </servlet>
> >
> > <servlet-mapping>
> > <servlet-name>CocoonServlet</servlet-name>
> > <url-pattern>/*</url-pattern>
> > </servlet-mapping>
> >
> > </web-app>
> >
> > ======================
> > What should go in the cocoon.xconf ?
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
