You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@cocoon.apache.org by di...@apache.org on 2001/04/05 12:37:59 UTC
cvs commit: xml-cocoon INSTALL
dims 01/04/05 03:37:59
Modified: . Tag: xml-cocoon2 INSTALL
Log:
Updated INSTALL doc with info for precompiline Sitemap and XSP's
Revision Changes Path
No revision
No revision
1.1.2.5 +13 -1 xml-cocoon/Attic/INSTALL
Index: INSTALL
===================================================================
RCS file: /home/cvs/xml-cocoon/Attic/INSTALL,v
retrieving revision 1.1.2.4
retrieving revision 1.1.2.5
diff -u -r1.1.2.4 -r1.1.2.5
--- INSTALL 2001/03/29 11:13:40 1.1.2.4
+++ INSTALL 2001/04/05 10:37:56 1.1.2.5
@@ -92,7 +92,8 @@
Cocoon compiles sitemaps into java classes to increase runtime performance,
this is done only at startup and only if the sitemap file is modified, for
- all the other requests the compiled sitemap is executed.
+ 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?
@@ -128,6 +129,17 @@
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