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/docs faq.xml index.xml installing.xml xspprocessor.xml
Date Sat, 08 Jan 2000 00:09:33 GMT
stefano     00/01/07 16:09:32

  Modified:    docs     faq.xml index.xml installing.xml xspprocessor.xml
  Log:
  docs cleanups
  
  Revision  Changes    Path
  1.10      +4 -4      xml-cocoon/docs/faq.xml
  
  Index: faq.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/docs/faq.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- faq.xml	2000/01/03 01:34:34	1.9
  +++ faq.xml	2000/01/08 00:09:31	1.10
  @@ -7,8 +7,8 @@
   <faq>
    <question>How do I pipe my servlet output into Cocoon?</question>
    <answer>
  -  <p>Simple answer: <em>you don't!!!</em> read <connect href="dynamic.xml">this
  -  document</connect> instead to find out equivalent ways to do what you need.</p>
  +  <p>Simple answer: <em>you don't!!!</em> read <connect href="dynamic.xml">the
page
  +  about dynamic content</connect> to find out equivalent ways to do what you need.</p>
     <p>Complex answer: the Servlet API <em>was not</em> designed with servlet
     chaining capabilities in mind. Servlet chaining was a night hack of the
     original Java web server authors that allowed to pipe one servlet output
  @@ -36,7 +36,7 @@
     <ul>
       <li><link href="http://www.xml.org">http://www.xml.org</link> - A
very nice site for XML
         information.</li>
  -    <li><link href="http://www.w3.org/markup/xml/">http://www.w3.org/markup/xml/</link>
- The XML
  +    <li><link href="http://www.w3.org/xml/">http://www.w3.org/xml/</link>
- The XML
         official home page at W3C</li>
       <li><link href="http://www.w3.org/style/xsl">http://www.w3.org/style/xsl</link>
- The XSL official
         home page W3C</li>
  @@ -149,7 +149,7 @@
       processing chain for each requested URI and for every possible request state
       (with request parameters, session parameters and environment parameters).</p>
     <p>The proposed solution (as you read in the <connect href="cocoon2.xml">Cocoon2
  -    outline</connect>) is to have a regular expression based site map where site
  +    outline</connect>) is to have a site map where site
       managers decide what processing chain to apply to each possible request.
       This somehow follows the mod_rewrite model in the Apache Web Server, but
       rather than URL rewriting, the site map allows site designers to control the
  
  
  
  1.8       +6 -13     xml-cocoon/docs/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/docs/index.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- index.xml	2000/01/03 01:34:34	1.7
  +++ index.xml	2000/01/08 00:09:31	1.8
  @@ -115,15 +115,6 @@
      of special cache systems.
     </p>
     <p>
  -   In this direction it must be understood that Cocoon 1.x should
  -   be considered a proof of concept rather than a software usable for real web
  -   sites. In fact, the Cocoon projects aims to gather as much information as
  -   possible during it's first generation while its second generation, starting
  -   from Cocoon 2.0, will aim to be a usable and real-life publishing framework.
  -   See the <connect href="cocoon2.xml">Cocoon 2 outline</connect> to understand
the 
  -   design plans already established.
  -  </p>
  -  <p>
      Another problem is the intrinsic impossibility of page-compiling all the three
      processing layers, due to the post-processing requirements of XSL styling. This 
      problem will be solved (hopefully!) with the availability of XSL-enabled
  @@ -155,9 +146,11 @@
      (follow the link for information on how to subscribe and to access the mail 
      list archives), to checkout the <link href="http://xml.apache.org/websrc/cvsweb.cgi/xml-cocoon/">
      latest and greatest code</link> (which you found in the xml-cocoon module in 
  -   the xml.apache.org CVS code repository), control the <connect href="../todo.xml">todo</connect>
  +   the xml.apache.org CVS code repository, or from the 
  +   <link href="http://xml.apache.org/from-cvs/xml-cocoon/">CVS snapshots</link>),

  +   control the <connect href="../todo.xml">todo</connect>
      list and jump in. Document writers are usually the most wanted people so if
  -   you like to help but you're not familiar with technical details, don't worry
  +   you like to help but you're not familiar with technical details, don't worry:
      we have work for you.
     </p>
     <p>
  @@ -173,9 +166,9 @@
     </p>
     <p>
      Anyway, a great way of contributing back to the project is to
  -   allow others to know about it so that the word spreads and other may wish to
  +   allow others to know about it so that the word spreads and others may wish to
      contribute, so, please, help us by placing the cocoon logo somewhere in your
  -   site to indicate that you are using uses and supporting the Cocoon Project.
  +   site to indicate that you are using and supporting the Cocoon Project.
     </p>
     
     <p>
  
  
  
  1.14      +5 -5      xml-cocoon/docs/installing.xml
  
  Index: installing.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/docs/installing.xml,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- installing.xml	2000/01/06 15:15:01	1.13
  +++ installing.xml	2000/01/08 00:09:31	1.14
  @@ -193,14 +193,14 @@
      <ul>
       <li>Startup heap size:
        <ul>
  -      <li>java 1.1 - <code>-ms[size]</code>
  -      <li>java 1.2 - <code>-Xms[size]</code>
  +      <li>java 1.1 - <code>-ms[size]</code></li>
  +      <li>java 1.2 - <code>-Xms[size]</code></li>
        </ul>
       </li>
       <li>Maximum heap size:
        <ul>
  -      <li>java 1.1 - <code>-mx[size]</code>
  -      <li>java 1.2 - <code>-Xmx[size]</code>
  +      <li>java 1.1 - <code>-mx[size]</code></li>
  +      <li>java 1.2 - <code>-Xmx[size]</code></li>
        </ul>
       </li>
      </ul>
  @@ -231,7 +231,7 @@
       locate this directory somewhere else, you have to change the
      </p>
      
  -<source>processor.xsp.repository = ./repository</store>
  +<source>processor.xsp.repository = ./repository</source>
   
      <p>
       property in the cocoon configuration file.
  
  
  
  1.3       +0 -124    xml-cocoon/docs/xspprocessor.xml
  
  Index: xspprocessor.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/docs/xspprocessor.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- xspprocessor.xml	2000/01/05 13:49:12	1.2
  +++ xspprocessor.xml	2000/01/08 00:09:31	1.3
  @@ -1690,130 +1690,6 @@
         </p>
       </s1>
   
  -    <s1 title="Installation and Configuration">
  -      <p>
  -        XSP is currently in an early development
  -	stage.
  -      </p>
  -
  -      <p>
  -        As such, some of the functionality described
  -	in this document may be buggy or incomplete.
  -      </p>
  -
  -      <p>
  -        So far, XSP has been tested only with:
  -      </p>
  -
  -      <ul>
  -	<li>Cocoon 1.6 dev</li>
  -	<li>The <em>Xerces</em> XML parser</li>
  -	<li>The <em>Xalan</em> XSLT processor</li>
  -      </ul>
  -
  -      <p>
  -        XSP requires the following properties
  -	to be added to your
  -	<em>cocoon.properties</em>
  -	configuration file:
  -      </p>
  -
  -      <source># Apache Xerces 1.0.1+ (http://xml.apache.com/)
  -parser = org.apache.cocoon.parser.XercesParser
  -
  -# Apache Xalan (http://xml.apache.org/)
  -transformer = org.apache.cocoon.transformer.XalanTransformer
  -
  -# eXtensible Server Pages Processor (XSP)
  -processor.type.xsp= org.apache.cocoon.processor.xsp.XSPProcessor
  -processor.xsp.repository = <em>PATH_TO_XSP_CLASS_STORE</em>
  -processor.xsp.libraries = <em>PATH_TO</em>/xsp-libraries.xml
  -</source>
  -
  -      <p>
  -        The <em>XSP repository</em> is a
  -	<em>physical</em> (not virtual!)
  -	filesystem directory that will
  -	contain the generated Java source
  -	and class files. This directory
  -	<em>must</em> exist in advance
  -	and must be readable and writable
  -	by the operating system user running
  -	the servlet engine and/or web server
  -	processes.
  -      </p>
  -
  -      <p>
  -       Thus, in the above
  -       <em>cocoon.properties</em>
  -       configuration file,
  -         <em>PATH_TO_XSP_CLASS_STORE</em>
  -        must be replaced by the correct
  -	location of this directory.
  -      </p>
  -
  -      <p>
  -        The file <code>xsp-libraries.xml</code>
  -	is an XML configuration file containing
  -	a list of XSP library descriptors.
  -	This file must exist and must be
  -	readable by the operating system user
  -	running the servlet engine
  -	and/or web server processes.
  -      </p>
  -
  -      <p>
  -        The <code>xsp-libraries.xml</code>
  -	included in the initial XSP distribution 
  -	contains:
  -      </p>
  -
  -      <source>&lt;?xml version="1.0"?&gt;
  -&lt;xsp-libraries&gt;
  -  &lt;library namespace="util"&gt;
  -    &lt;template language="java" stylesheet="util-java.xsl"/&gt;
  -  &lt;/library&gt;
  -  &lt;library namespace="xbean"&gt;
  -    &lt;template
  -      language="java"
  -      stylesheet="xbean-java.xsl"
  -      preprocessor="org.apache.cocoon.processor.xsp.xbean.XBeanPreprocessor"
  -    /&gt;
  -  &lt;/library&gt;
  -&lt;/xsp-libraries&gt;
  -</source>
  -
  -      <p>
  -        Note that the stylesheet file
  -	<code>util-java.xsl</code>
  -	will be located relative to
  -	the location of the
  -	<code>xsp-libraries.xml</code>
  -	file.
  -      </p>
  -
  -      <p>
  -        If you want to place a library
  -	stylesheet file in a different
  -	location, you must specify its
  -	fully qualified pathname. Example:
  -      </p>
  -
  -      <source>. . .
  -&lt;library namespace="util"&gt;
  -  &lt;template language="java" stylesheet="/usr/local/apache/lib/util-java.xsl"/&gt;
  -&lt;/library&gt;
  -. . . </source>
  -
  -      <p>
  -        Also, if your library requires a
  -	preprocessor class, it must be
  -	accessible to the servlet engine
  -	through its <code>CLASSPATH</code>
  -	system property.
  -      </p>
  -    </s1>
  -
       <s1 title="Acknowledgements">
         <p>
           This initial implementation of XSP has
  
  
  

Mime
View raw message