cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From stef...@locus.apache.org
Subject cvs commit: xml-cocoon/xdocs faq.xml installing.xml
Date Mon, 14 Feb 2000 12:21:14 GMT
stefano     00/02/14 04:21:14

  Modified:    .        build.xml changes.xml
               lib      ant.jar
               src/org/apache/cocoon cocoon.properties
               xdocs    faq.xml installing.xml
  Log:
  - patched ant
  - better build file
  - cleaner docs
  - almost ready for 1.7
  
  Revision  Changes    Path
  1.32      +25 -16    xml-cocoon/build.xml
  
  Index: build.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/build.xml,v
  retrieving revision 1.31
  retrieving revision 1.32
  diff -u -r1.31 -r1.32
  --- build.xml	2000/02/14 01:03:23	1.31
  +++ build.xml	2000/02/14 12:21:11	1.32
  @@ -177,6 +177,7 @@
   
       <filter token="year" value="${year}"/>
       <filter token="version" value="${version}"/>
  +    <filter token="date" value="${TODAY}"/>
     </target>
   
     <!-- =================================================================== -->
  @@ -216,15 +217,24 @@
     <!-- Prepares the build directory                                        -->
     <!-- =================================================================== -->
     <target name="prepare-xt" if="xt.present">
  -    <copydir src="${src.dir}" dest="${build.src}" includes="**/XT*"/>
  +    <copydir src="${src.dir}"
  +             dest="${build.src}"
  +             includes="**/XT*"
  +             filtering="on"/>
     </target>
   
     <target name="prepare-ldap" if="jndi.present">
  -    <copydir src="${src.dir}" dest="${build.src}" includes="**/ldap/**"/>
  +    <copydir src="${src.dir}"
  +             dest="${build.src}"
  +             includes="**/ldap/**"
  +             filtering="on"/>
     </target>
   
     <target name="prepare-ecma" if="fesi.present">
  -    <copydir src="${src.dir}" dest="${build.src}" includes="**/ecmascript/**"/>
  +    <copydir src="${src.dir}"
  +             dest="${build.src}"
  +             includes="**/ecmascript/**"
  +             filtering="on"/>
     </target>
   
     <!-- =================================================================== -->
  @@ -236,7 +246,10 @@
       <mkdir dir="${build.dest}"/>
   
       <!-- copy src files -->
  -    <copydir src="${src.dir}" dest="${build.src}" excludes="**/XT*, **/ldap/**, **/ecmascript/**"/>
  +    <copydir src="${src.dir}"
  +             dest="${build.src}"
  +             excludes="**/XT*, **/ldap/**, **/ecmascript/**"
  +             filtering="on"/>
     </target>
   
     <!-- =================================================================== -->
  @@ -263,14 +276,11 @@
     <!-- Prepares the docs                                                   -->
     <!-- =================================================================== -->
     <target name="prepare-docs">
  -    <copyfile src="changes.xml" dest="${docs.dir}/changes.xml"/>
  +    <copyfile src="changes.xml" dest="${docs.dir}/changes.xml" filtering="on"/>
       <copyfile src="todo.xml" dest="${docs.dir}/todo.xml"/>
   
       <replace file="${docs.dir}/changes.xml" token="./docs/dtd/" value="dtd/"/>
       <replace file="${docs.dir}/todo.xml" token="./docs/dtd/" value="dtd/"/>
  -
  -    <replace file="${docs.dir}/changes.xml" token="${version}-dev" value="${version}"/>
  -    <replace file="${docs.dir}/changes.xml" token="Not yet released" value="${TODAY}"/>
     </target>
   
     <!-- =================================================================== -->
  @@ -278,7 +288,7 @@
     <!-- =================================================================== -->
     <target name="docs" depends="prepare-docs">
       <mkdir dir="${build.docs}"/>
  -    <copyfile src="${docs.dir}/docs-book.xml" dest="${docs.dir}/book.xml"/>
  +    <copyfile src="${docs.dir}/docs-book.xml" dest="${docs.dir}/book.xml" filtering="on"/>
       <java fork="yes" classpath="${java.class.path}:${doc.generator.package}" class="${doc.generator}"
             args="targetDirectory=${build.docs} ${docs.dir}/book.xml ${skin}"/>
     </target>
  @@ -288,7 +298,7 @@
     <!-- =================================================================== -->
     <target name="site" depends="prepare-docs">
       <mkdir dir="${site.dir}"/>
  -    <copyfile src="${docs.dir}/site-book.xml" dest="${docs.dir}/book.xml"/>
  +    <copyfile src="${docs.dir}/site-book.xml" dest="${docs.dir}/book.xml" filtering="on"/>
       <java fork="yes" classpath="${java.class.path}:${doc.generator.package}" class="${doc.generator}"
             args="targetDirectory=${site} ${docs.dir}/book.xml ${skin}"/>
     </target>
  @@ -334,16 +344,15 @@
       <copydir src="${build.javadocs}" dest="${dist.dir}/docs/api"/>
       <copydir src="${samples.dir}" dest="${dist.dir}/samples"/>
       <copydir src="${docs.dir}" dest="${dist.dir}/xdocs" excludes="book.xml, changes.xml,
todo.xml"/>
  +    <copydir src="${docs.dir}" dest="${dist.dir}" includes="changes.xml, todo.xml"/>
       <copydir src="${skins.dir}" dest="${dist.dir}/skins"/>
       <copydir src="${lib.dir}" dest="${dist.dir}/lib"/>
  -
  -    <copyfile src="README" dest="${dist.dir}/README"/>
  -    <copyfile src="LICENSE" dest="${dist.dir}/LICENSE"/>
   
  -    <copydir src="." dest="${dist.dir}" includes="build.*"/>
  +    <copydir src="." dest="${dist.dir}" includes="README, LICENSE, build.*" filtering="on"/>
   
  -    <copyfile src="${docs.dir}/changes.xml" dest="${dist.dir}/changes.xml"/>
  -    <copyfile src="${docs.dir}/todo.xml" dest="${dist.dir}/todo.xml"/>
  +    <chmod perm="+x" src="${dist.dir}/build.sh"/>
  +    <fixcrlf srcdir="${dist.dir}" includes="build.sh" cr="remove"/>
  +    <fixcrlf srcdir="${dist.dir}" includes="build.bat" cr="add"/>
     </target>
   
     <!-- =================================================================== -->
  
  
  
  1.30      +2 -2      xml-cocoon/changes.xml
  
  Index: changes.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/changes.xml,v
  retrieving revision 1.29
  retrieving revision 1.30
  diff -u -r1.29 -r1.30
  --- changes.xml	2000/02/14 01:03:23	1.29
  +++ changes.xml	2000/02/14 12:21:11	1.30
  @@ -4,7 +4,7 @@
   
   <!--
     History of Cocoon changes
  -  $Id: changes.xml,v 1.29 2000/02/14 01:03:23 stefano Exp $
  +  $Id: changes.xml,v 1.30 2000/02/14 12:21:11 stefano Exp $
   -->
   
   <changes title="History of Changes">
  @@ -14,7 +14,7 @@
       <person name="Ricardo Rocha" email="rrocha@apache.org" id="RR"/>
     </devs>
   
  - <release version="1.7-dev" date="Not yet released">
  + <release version="@version@" date="@date@">
     <action dev="SM" type="fix">
       Patched memory usage and tested under heavy load.
     </action>
  
  
  
  1.4       +147 -140  xml-cocoon/lib/ant.jar
  
  	<<Binary file>>
  
  
  1.15      +0 -3      xml-cocoon/src/org/apache/cocoon/cocoon.properties
  
  Index: cocoon.properties
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/src/org/apache/cocoon/cocoon.properties,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- cocoon.properties	2000/02/14 00:59:18	1.14
  +++ cocoon.properties	2000/02/14 12:21:13	1.15
  @@ -122,9 +122,6 @@
   # LDAP Processor
   processor.type.ldap = org.apache.cocoon.processor.ldap.LdapProcessor
   
  -# NOTE: see the LDAP processor user guide for the packages required for
  -# this processor.
  -
   
   #### !!!!WARNING!!!! ###########
   # The DCP processor should be considered -deprecated- and we highly suggest
  
  
  
  1.2       +79 -32    xml-cocoon/xdocs/faq.xml
  
  Index: faq.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/xdocs/faq.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- faq.xml	2000/01/27 03:46:03	1.1
  +++ faq.xml	2000/02/14 12:21:14	1.2
  @@ -5,21 +5,68 @@
   <faqs title="Frequently Asked Questions">
   
   <faq>
  - <question>Previous Cocoon releases said that this product was to consider a 
  - proof of concept rather than a working solution. I can't find that sentence
  - anymore. What happened?</question>
  - <answer>
  -  <p>We believe that Cocoon has entered the final stage of its evolution but
  -  as it stands today, it is ready to be used for a production environment.</p>
  -  <p>Careful, we don't say it's perfect or bug-free, this is impossible to say,
  -  but at least, we think this technology is good enough for you to try it out
  -  against other solutions for web publishing.</p>
  -  <p>Warning: this doesn't mean that Cocoon evolution came to an end, not at all,
  -  but that we believe it's mature enough to be deployed in a working environment
  -  with no particular problems.</p>
  -  <p>Note, however, that this software comes "as is" so you should always be
  -  aware of the risks as for any other open source software, but I think that
  -  if you read this, you already know what we mean :)</p>
  + <question>I keep on getting OutOfMemoryErrors but I've given the JVM
  + a lot of memory. Are you sure this is not a memory leak? How do I fix this, then?
  + </question>
  + <answer>
  +  <p>This is not a memory leak but an expected behavior. Which means: you can
  +  tune the Cocoon configurations to avoid this.</p>
  +  <p>The key is the <code>store.memory</code> configuration. This tells
cocoon
  +  to leave that much memory to the system for normal operation. Everything
  +  else is taken by the memory cache!</p>
  +  <p>If the <code>store.memory</code> configuration is lower than the
amount
  +  of memory required to process the running requests (all of them together!)
  +  it might happen (Cocoon tries to do some cache garbage collection if this
  +  happens) that OutOfMemoryErrors are triggered.</p>
  +  <p>If the problem persist even highering your store memory, then it's a bug
  +  and it should not happen.</p>
  +  <note>Since Cocoon 1.7, garbage collection was added to the cache system
  +  and this should prevent these OutOfMemory on almost all the possible circumstances</note>
  + </answer>
  +</faq>
  +
  +<faq>
  + <question>I can't get XSP to work. What might be wrong?</question>
  + <answer>
  +  <p>
  +   The XSP processor requires a single configuration that might cause problems:
  +   the repository location for compiled server pages.
  +  </p>
  +
  +<source>processor.xsp.repository = ./repository</source>
  +
  +  <p>
  +   If the process that runs the servlet engine doesn't have both reading
  +   and writing persmissions on that directory, the XSP processor won't work, so
  +   make sure you locate that directory to a safe place.
  +  </p>
  +
  +  <note><strong>Warning:</strong>
  +    Since this directory may contain security sensible information, make sure
  +    you deny access (even read-only) to untrusted users.
  +  </note>
  + </answer>
  +</faq>
  +
  +<faq>
  + <question>Why the LDAP processor doesn't work?</question>
  + <answer>
  +  <p>Make sure you have the <link href="http://java.sun.com/products/jndi/index.html">Sun
JNDI API</link>
  +   package installed in your classpath.</p>
  + </answer>
  +</faq>
  +
  +<faq>
  + <question>Why DCP doesn't work with EcmaScript anymore?</question>
  + <answer>
  +  <p>Since Cocoon now ships with all the required packages and Fesi is a
  +  very big package, we decided to make Ecmascript support for DCP optional.</p>
  +  <p>So, you should turn on the language interpretation in the cocoon
  +  configurations and place the <link href="http://home.worldcom.ch/jmlugrin/fesi/download.html">
  +  FESI</link> package in your classpath.</p>
  +  <note>the DCP processor should be considered deprecated and we do not guarantee
  +  that will be supported in future versions. We highly suggest you to
  +  transfor all of your DCP pages into XSP pages.</note>
    </answer>
   </faq>
   
  @@ -47,10 +94,10 @@
     since Cocoon is a servlet, there is no portable way for it to call
     your servlet and to process its output.</p>
     <p>The Cocoon Project is in close contact with the Servlet API Expert Group at
  -  Sun (being Stefano Mazzocchi a member of that board) and will propose 
  -  post-processing hooks for inclusion in the next Servlet API specifications. 
  -  Since this is work in progress, please, don't fill up the mail list with 
  -  questions about this: Cocoon will reflect the API changes as soon as they 
  +  Sun (being Stefano Mazzocchi a member of that board) and will propose
  +  post-processing hooks for inclusion in the next Servlet API specifications.
  +  Since this is work in progress, please, don't fill up the mail list with
  +  questions about this: Cocoon will reflect the API changes as soon as they
     are publicly available.</p>
    </answer>
   </faq>
  @@ -93,7 +140,7 @@
   <faq>
    <question>Are there document translations to other languages?</question>
    <answer>
  -  <p>Given the problems we already have with documentation (which is never big and
good enough), 
  +  <p>Given the problems we already have with documentation (which is never big and
good enough),
     the Cocoon Project uses English as its standard and only documentation language. This
is also
     the only language used in the mail lists. Also, the Cocoon distribution will contain
     English documentation only to reduce updating problems.</p>
  @@ -120,11 +167,11 @@
     <p>You must apply this patch to Tomcat 3.0 and recompile it or it won't work.
     This patch is already present in latest CVS code but in case you don't want
     to download the latest code you can apply this:</p>
  -  
  +
     <source><![CDATA[ Index: RequestMapper.java
      ===================================================================
      RCS file: /home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/core/RequestMapper.java,v
  - 
  +
      retrieving revision 1.5
      retrieving revision 1.6
      diff -u -r1.5 -r1.6
  @@ -143,7 +190,7 @@
      -            }
      +            mapPath = this.resourceName;
               }
  - 
  +
               return mapPath;]]></source>
    </answer>
   </faq>
  @@ -158,7 +205,7 @@
   </faq>
   
   <faq>
  - <question>I see that Cocon 1.x has starting to incorporate features planned for

  + <question>I see that Cocon 1.x has starting to incorporate features planned for
    Cocoon 2.x, why?</question>
    <answer>
     <p>We believe that smooth project evolution is much better than step-wise
  @@ -188,7 +235,7 @@
     technology is rapidly changing and your books should warn you that the topic they are
     discussing is not even in W3C Recommendation state. Which means that more changes are
on
     their way.</p>
  -  <p>The current and proper way to associate a stylesheet with an XML document can
be found at 
  +  <p>The current and proper way to associate a stylesheet with an XML document can
be found at
     <link href="http://www.w3.org/TR/xml-stylesheet">http://www.w3.org/TR/xml-stylesheet</link>
and
     clearly indicates that <code>&lt;?xml-stylesheet ...?&gt;</code>
is the proper way.</p>
    </answer>
  @@ -223,9 +270,9 @@
   <question>What is WAP and how do I browse WML?</question>
   <answer>
     <p>WAP stands for Wireless Application Protocol and WML stands for Wireless
  -    Markup Language. For more information about these two, please refer to the 
  -    <link href="http://www.wapforum.org">WAP Forum</link>. For a client able

  -    to browse WML 1.1, Cocoon has been tested with the 
  +    Markup Language. For more information about these two, please refer to the
  +    <link href="http://www.wapforum.org">WAP Forum</link>. For a client able
  +    to browse WML 1.1, Cocoon has been tested with the
       <link href="http://www.nokia.com">Nokia WAP Toolkit</link> which
       emulates a Nokia WAP cell phone on your desktop.</p>
   </answer>
  @@ -234,9 +281,9 @@
   <faq>
   <question>What is VoxML and how do I browse VML?</question>
   <answer>
  -  <p>VoxML is a voice markup language, designed to allow direct integration 
  -    between voice recognition/synthesis software and web technologies. 
  -    The Cocoon VML samples have been tested with the 
  +  <p>VoxML is a voice markup language, designed to allow direct integration
  +    between voice recognition/synthesis software and web technologies.
  +    The Cocoon VML samples have been tested with the
       <link href="http://www.voxml.org">Motorola VoxML SDK 1.1</link>(for windows)
       which is freely available.</p>
   </answer>
  @@ -245,7 +292,7 @@
   <faq>
   <question>Why is my Internet Explorer not showing PDF or VRML samples?</question>
   <answer>
  -  <p>This is a long-time problem with internet explorer which, illegally, 
  +  <p>This is a long-time problem with internet explorer which, illegally,
     reacts on URI extention rathen than returned MIME type. The only think you can
     do for now is to map .pdf or .wrl to Cocoon for handling, but we know that
     sucks. Don't worry, in the future, the sitemap proposal will allow you
  
  
  
  1.4       +24 -129   xml-cocoon/xdocs/installing.xml
  
  Index: installing.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/xdocs/installing.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- installing.xml	2000/02/13 18:29:43	1.3
  +++ installing.xml	2000/02/14 12:21:14	1.4
  @@ -58,9 +58,9 @@
     </p>
   
     <note>
  -   Then Ant and Stylebook packages are only used in the build system and
  +   The Ant and Stylebook packages are only used in the build system and
      are <strong>not</strong> used by Cocoon at run-time. So you can safely
  -   leave them out of your servlet engine classpath.
  +   ignore them in the installation.
     </note>
    </s1>
   
  @@ -73,102 +73,12 @@
      servlet systems.
     </p>
   
  -  <s2 title="General considerations">
  -   <p>
  -    There are some general considerations that apply to all systems.
  -   </p>
  -
  -   <p>
  -    Since there is no portable way, in a Java platform, to tell how much memory an object
  -    is using, the memory cache works in a rather cumbersome manner:  you set up
  -    a lower limit that the cache must always leave free for the JVM operation.
  -    This means, that if the memory limit is 200Kb, Cocoon uses all your JVM
  -    heap size to store pages in memory and makes sure that 200Kb are available
  -    for other operations.
  -   </p>
  -
  -   <p>
  -    This does not impact the JVM operation, if enough memory is left for the
  -    normal operation. You must be aware of the fact that leaving Cocoon with
  -    too little memory for operation does impact peformance since the JVM
  -    garbage collector has to do more work to keep up with execution and
  -    memory cleanup. Sometimes, you may even end up having OutOfMemoryExceptions
  -    if your limit is lower than the memory required for the operation.
  -   </p>
  -
  -   <p>
  -    A good way to control your memory is to setup your JVM with a fixed
  -    heap limit and to give it enough memory to start. This is done by using
  -    command line parameters for your java interpreter such as:
  -   </p>
  -
  -   <ul>
  -    <li>Startup heap size:
  -     <sl>
  -      <li>java 1.1 - <code>-ms[size]</code></li>
  -      <li>java 1.2 - <code>-Xms[size]</code></li>
  -     </sl>
  -    </li>
  -    <li>Maximum heap size:
  -     <sl>
  -      <li>java 1.1 - <code>-mx[size]</code></li>
  -      <li>java 1.2 - <code>-Xmx[size]</code></li>
  -     </sl>
  -    </li>
  -   </ul>
  -
  -   <p>
  -    A well balanced system should have something like 8Mb start heap, 2Mb
  -    Cocoon memory limit and 64Mb or greater max heap, but these depend heavily
  -    on your system load/configuration to be generally meaningful.
  -   </p>
  -
  -   <p>
  -    To change the cocoon object store memory limit open you should change the
  -    following property in the <code>cocoon.properties</code> file.
  -   </p>
  -
  -<source>store.memory = 200000</source>
  -
  -   <p>
  -    Another important part of Cocoon is the page compiler used inside the
  -    XSP processor which store the generated/compiled pages on file system.
  -    The default directory is <code>./repository</code> which is usually relative
  -    to the web server or servlet engine working directory.
  -   </p>
  -
  -   <p>
  -    If you experience
  -    troubles (such as not having reading/writing permissions) or you want to
  -    locate this directory somewhere else, you have to change the
  -   </p>
  -
  -<source>processor.xsp.repository = ./repository</source>
  -
  -   <p>
  -    property in the cocoon configuration file.
  -   </p>
  -
  -   <p><strong>Warning:</strong>
  -    Since this directory may contain security sensible information, make sure
  -    you deny access (even read-only) to untrusted users.
  -   </p>
  -  </s2>
  -
     <s2 title="Installing Cocoon on Apache JServ">
      <p>
  -    Apache JServ has one configuration file for the whole engine (normally called
  -    <code>jserv.properties</code>) and one for each servlet zone. Please, refer
  -    to the Apache JServ documentation for more information on this.
  -   </p>
  -
  -   <p>
       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 line like this in your
  -    <code>jserv.properties</code> file for each jar package you have to install
  -    (after substituting <em>[path-to-jar]</em> with the path to the jar file
and
  -    <em>[jar-name]</em> with the package file name).
  +    this to the servlet engine classpath by adding a bunch of classpath lines
  +    to your <code>jserv.properties</code> file for each jar package.
      </p>
   
   <source>wrapper.classpath=[path-to-jar]/[jar-name].jar</source>
  @@ -193,18 +103,14 @@
   
      <p>
       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 (Note that
  -    Cocoon can safely reside on different servlet zones with different
  -    configuration files). If you don't know what a servlet zone is, you
  -    probably want to open the <code>zone.properties</code> file that represents
  -    the default servlet zone.
  +    must choose the servlet zone(s) where you want Cocoon to reside.
  +    If you don't know what a servlet zone is, open the
  +    <code>zone.properties</code> file.
      </p>
   
      <p>
       To configure Cocoon, you must pass the <code>cocoon.properties</code>
  -    file location to the servlet by adding the following to the
  -    <code>zone.properties</code> file (or each servlet zone file you want
  -    Cocoon to reside):
  +    file location to the servlet by adding the following line to the servlet zone:
      </p>
   
   <source>servlet.org.apache.cocoon.Cocoon.initArgs=properties=[path-to-cocoon]/bin/cocoon.properties</source>
  @@ -221,50 +127,38 @@
       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 <code>mod_jserv.conf</code> or <code>jserv.conf</code>
file:
  +    to your <code>jserv.conf</code> file:
      </p>
   
   <source>Action cocoon /servlet/org.apache.cocoon.Cocoon
   AddHandler cocoon xml</source>
   
      <p>
  -    where <em>xml</em> is the file extention you want to map to the servlet
  +    where <em>xml</em> is the file extention you want Cocoon to handle
       and <em>/servlet/</em> is the mount point of your servlet zone (and the
       above is the standard name for servlet mapping for Apache JServ).
      </p>
   
      <p>
  -    At this point, you should check if your system matches the global
  -    considerations about Cocoon properties. Usually, you might want to give
  -    the installation a try as it is and then read again that section if
  -    something goes wrong. Most installations don't need any changes to
  -    be operational.
  +    Restart both Apache and Apache JServ and try accessing the Cocoon status page:
      </p>
   
  -   <p>
  -    Everything should be configured fine. Restart both Apache and Apache JServ
  -    and try accessing the samples contained in the distribution to see
  -    Cocoon in action or the <code>/Cocoon.xml</code> page for Cocoon internal
  -    status.
  -   </p>
  +<source>http://localhost/Cocoon.xml</source>
   
      <p>
  -    <strong>Note</strong>: you may want Cocoon to handle two different
  -    extentions with different configurations. To do this, you must set the two
  -    different configurations in two different servlet zones, then associate the
  -    extentions like this:
  +    Cocoon will show you how it's configured.
      </p>
   
  -<source>Action cocoon1 /zone1/org.apache.cocoon.Cocoon
  -Action cocoon1 /zone2/org.apache.cocoon.Cocoon
  -AddHandler cocoon1 xml1
  -AddHandler cocoon2 xml2</source>
  -
      <p>
  -    where <em>xml1</em> is handled by the Cocoon residing on <em>zone1</em>
  -    and <em>xml2</em> is handled by the Cocoon residing on <em>zone2</em>
  -    which have different configurations and thus different behavior.
  +    If the page above is working, place the samples contained in the distribution
  +    (under <code>./samples</code>) in your web server URI space and call
  +    <code>index.xml</code> to see Cocoon in action.
      </p>
  +
  +   <note>
  +    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.
  +   </note>
     </s2>
   
     <s2 title="Installing Cocoon on Apache Tomcat">
  @@ -558,8 +452,9 @@
      like servlet engines and servlet execution.
     </note>
     <p>
  -   Please, submit your feedback if you were able to install Cocoon on a
  -   different combination not listed above. Thanks.
  +   Please, submit your feedback on the cocoon user mail list (nowhere else!) if
  +   you were able to install Cocoon on a different combination not listed above.
  +   Thanks.
     </p>
    </s1>
   </body>
  
  
  

Mime
View raw message