You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@cocoon.apache.org by st...@apache.org on 2001/12/11 22:16:53 UTC
cvs commit: xml-cocoon2 INSTALL
stefano 01/12/11 13:16:53
Modified: . INSTALL
Log:
updated to avoid flooding cocoon-user
Revision Changes Path
1.3 +36 -23 xml-cocoon2/INSTALL
Index: INSTALL
===================================================================
RCS file: /home/cvs/xml-cocoon2/INSTALL,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- INSTALL 2001/07/19 09:52:25 1.2
+++ INSTALL 2001/12/11 21:16:53 1.3
@@ -86,7 +86,7 @@
7) Wait a few seconds (Cocoon needs to compile parts of itself when launched)
- 8) Say hallo to Cocoon :)
+ 8) Say hello to Cocoon :)
@@ -114,24 +114,46 @@
this is done only at startup and only if the sitemap file is modified, for
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) Why is cocoon.war so big?
+ 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?
+
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
which must be present in the war file to allow page compilation without
classloading problems.
-
- 4) I get a java.lang.VerifyError when accessing 'http://localhost/cocoon/'.
+
+
+ 5) 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.
- 5) I get an Exception when accessing Cocoon the first time. What's wrong?
+ 6) 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
@@ -142,24 +164,15 @@
tomcat/work directory beforehand.
- 6) I'm still stuck, what do I do?
+ 7) I'm still stuck, what do I do?
+
+ Read the Cocoon documentation included in the distribution.
+
+ This file is just a quick and dirty way to get you started but the docs
+ contain much more detailed information as well as FAQs and indications
+ on how to contact us.
+
- Well, contact the Cocoon Users mail list (cocoon-users@xml.apache.org).
- Please, do not contact developers directly for help since the user list are
- normally much more responsive and users normally have more experience in
- solving installation problems than developers do.
-
- 7) What are the steps to pre-compile the sitemap and XSP's?
-
- Step #1. 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>
- Step #2. Set the auto-reload to false in your sitemap.xmap as follows:
- <parameter name="auto-reload" value="false"/>
- Step #3. Use "-Dcompile.xsp=yes" in your build command line when you are
- building your WAR file.
Happy hacking with Apache Cocoon.
----------------------------------------------------------------------
In case of troubles, e-mail: webmaster@xml.apache.org
To unsubscribe, e-mail: cocoon-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-cvs-help@xml.apache.org