cziegeler 02/01/30 01:35:23
Modified: . INSTALL.bin INSTALL.src
Log:
Minor text updates
Revision Changes Path
1.2 +17 -76 xml-cocoon2/INSTALL.bin
Index: INSTALL.bin
===================================================================
RCS file: /home/cvs/xml-cocoon2/INSTALL.bin,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- INSTALL.bin 30 Jan 2002 09:29:22 -0000 1.1
+++ INSTALL.bin 30 Jan 2002 09:35:23 -0000 1.2
@@ -5,7 +5,8 @@
*-----------------------------*
- You have downloaded Cocoon and you don't like to read verbose docs, right?
+ You have downloaded the binary distribution of Cocoon and you don't like
+ to read verbose docs, right?
Great, this file is for you.
@@ -18,53 +19,8 @@
Done? Ok, let's go on.
-
- 2) Set your JAVA_HOME enviornment
-
- You have to set your JAVA_HOME enviornment to point to the root directory of
- the Java Development Kit 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, but you know how to setup enviornments, right?
-
-
- 3) Create the Cocoon WAR package.
-
- 3a) Automatic install.
-
- To create the package and automatically install it in your servlet
- container, do
-
- [unix] ./build.sh -Dinclude.webapp.libs=yes
-Dinstall.war=$TOMCAT_HOME/webapps install
- [win32] .\build.bat -Dinclude.webapp.libs=yes
-Dinstall.war=%TOMCAT_HOME%\webapps install
-
- This creates the "cocoon.war" file in '$TOMCAT_HOME/webapps' which
- is the absolute path to the location where the "cocoon.war" file
- should be deployed. It also changes all references to that directory
- in the included samples so that i.e. the database samples will work
- properly.
-
- Continue with 5)
-
- 3b) Manual install.
-
- To do this you simply have to type, depending on your operating system
-
- [unix] ./build.sh -Dinclude.webapp.libs=yes
-Dinstall.war=$TOMCAT_HOME/webapps webapp
- [win32] .\build.bat -Dinclude.webapp.libs=yes
-Dinstall.war=%TOMCAT_HOME%\webapps webapp
-
- This will create the "cocoon.war" file in the './build/cocoon'
- directory. It also changes all references to that directory in the
- included samples so that i.e. the database samples will work
- properly.
- TOMCAT_HOME points to the directory where tomcat is installed (note:
- you don't need to set it in the enviornment, it's there only to show
- you). For more information on Tomcat 3.2.1 see the FAQ below.
-
- 4) Install the WAR package in your servlet container.
+ 2) Install the WAR package in your servlet container.
There is no standard way to do this, but in most servlet engines, this is
just a matter of copying the war file in a specific directory and the
@@ -73,8 +29,8 @@
For Apache Tomcat, you have to copy the WAR archive into the '/webapps'
directory, so do
- [unix] cp ./build/cocoon/cocoon.war $TOMCAT_HOME/webapps/cocoon.war
- [win32] copy .\build\cocoon\cocoon.war %TOMCAT_HOME%\webapps\cocoon.war
+ [unix] cp ./cocoon.war $TOMCAT_HOME/webapps/cocoon.war
+ [win32] copy .\cocoon.war %TOMCAT_HOME%\webapps\cocoon.war
5) Restart the servlet engine.
@@ -115,29 +71,8 @@
all the other requests the compiled sitemap is executed. See question #7
for information on how to pre-compile the sitemap and the XSP's.
-
- 3) Can I improve startup-time by precompiling the sitemap and XSP's?
-
- Sure, follow the instructions:
-
- a) Set the "work-directory" parameter in web.xml as follows:
-
- <init-param>
- <param-name>work-directory</param-name>
- <param-value>WEB-INF/classes</param-value>
- </init-param>
-
- b) Set the auto-reload to false in your cocoon.xconf file as follows:
-
- <parameter name="auto-reload" value="false"/>
-
- c) Use "-Dcompile.xsp=yes" in your build command line when you are
- building your WAR file. For example:
-
- ./build.sh -Dcompile.xsp=yes -Dinclude.webapp.libs=yes
-Dinstall.war=$TOMCAT_HOME/webapps install
-
-
- 4) Why is cocoon.war so big?
+
+ 3) Why is cocoon.war so big?
Cocoon.war includes all the libraries that it requires to run. They are
several megabytes of Java classes and it also includes the JDK javac compiler
@@ -145,15 +80,14 @@
classloading problems.
-
- 5) I get a java.lang.VerifyError when accessing 'http://localhost/cocoon/'.
+ 4) I get a java.lang.VerifyError when accessing 'http://localhost/cocoon/'.
What's wrong?
Make sure you do not have a Cocoon 1.x jar in your servlet container lib/
directory.
- 6) I get an Exception when accessing Cocoon the first time. What's wrong?
+ 5) I get an Exception when accessing Cocoon the first time. What's wrong?
Cocoon requires a JAXP 1.1 compliant parser. Recent servlet engines
(like Tomcat 3.2.1) use older xml parsers. You have to replace the xml
@@ -164,6 +98,13 @@
tomcat/work directory beforehand.
+ 8) I want to learn more about Cocoon.
+
+ Download the source distribution from http://xml.apache.org/dist/cocoon.
+ The source distribution contains everything you need in order to build
+ Cocoon yourself.
+
+
7) I'm still stuck, what do I do?
Read the Cocoon documentation included in the distribution.
@@ -172,7 +113,7 @@
contain much more detailed information as well as FAQs and indications
on how to contact us.
-
+
Happy hacking with Apache Cocoon.
1.2 +8 -2 xml-cocoon2/INSTALL.src
Index: INSTALL.src
===================================================================
RCS file: /home/cvs/xml-cocoon2/INSTALL.src,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- INSTALL.src 30 Jan 2002 09:29:22 -0000 1.1
+++ INSTALL.src 30 Jan 2002 09:35:23 -0000 1.2
@@ -5,7 +5,8 @@
*-----------------------------*
- You have downloaded Cocoon and you don't like to read verbose docs, right?
+ You have downloaded the source distribution of Cocoon and you don't like
+ to read verbose docs, right?
Great, this file is for you.
@@ -163,8 +164,13 @@
it to parser.jar. Before you restart Tomcat make sure to remove the
tomcat/work directory beforehand.
+ 7) I don't want to build Cocoon myself.
- 7) I'm still stuck, what do I do?
+ Download the binary distribution from http://xml.apache.org/dist/cocoon.
+ The binary distribution contains a pre-build war file of Cocoon.
+
+
+ 8) I'm still stuck, what do I do?
Read the Cocoon documentation included in the distribution.
----------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
