cocoon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gree...@locus.apache.org
Subject cvs commit: xml-cocoon/xdocs mail-lists.xml connection-pool.xml docs-book.xml faq.xml index.xml installing.xml infrastructure.xml site-book.xml
Date Fri, 22 Sep 2000 22:57:00 GMT
greenrd     00/09/22 15:56:59

  Modified:    .        README todo.xml
               skins/xml.apache.org/stylesheets document2html.xsl
               xdocs    connection-pool.xml docs-book.xml faq.xml index.xml
                        installing.xml infrastructure.xml site-book.xml
  Added:       xdocs    mail-lists.xml
  Log:
  minor docs improvements
  
  Revision  Changes    Path
  1.8       +50 -6     xml-cocoon/README
  
  Index: README
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/README,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- README	2000/02/13 18:29:11	1.7
  +++ README	2000/09/22 22:56:45	1.8
  @@ -1,9 +1,18 @@
   
  -                        C   O   C   O   O   N 
  -                        
  +                        C   O   C   O   O   N
  +
                                  @version@
  -                                
  -                      
  +
  +
  +Contents
  +
  +* What is it?
  +* Where is it?
  +* Requirements
  +* Release Notes for Cocoon 1.8
  +* Licensing and Legal Issues
  +
  +
     What is it?
     -----------
   
  @@ -44,10 +53,45 @@
     -------------------------------------------
   
     The documentation available as of the date of this release is
  -  included in the "docs/" directory.
  -  
  +  included in the "docs/" directory (unless you got this from CVS,
  +  in which case you need to run build docs, which generates documentation
  +  in the build/docs directory).
  +
     Look for the most updated documentation on the Cocoon web site under
     the Apache XML Project (http://xml.apache.org/cocoon/).
  +
  +
  +  Release Notes for Cocoon 1.8
  +  ----------------------------
  +
  +  There are no reported major issues with this release.
  +
  +  As usual, if upgrading from an earlier release, you need to replace your
  +  cocoon.properties file with the one supplied in
  +  src/org/apache/cocoon/cocoon.properties,
  +  (then make any site-specific adjustments if you have any),
  +  or Cocoon will very likely not work at all.
  +
  +  *** IMPORTANT ***
  +  If you get an error message about ProducerFromRequest, this means
  +  that you forgot to do the above. See the FAQ for more details.
  +
  +  Note also that you need an additional library, new to 1.8,
  +  turbine-pool.jar, which is in the /lib directory, to be visible
  +  to the servlet engine. See the installation instructions.
  +
  +  As usual, changes since previous releases are documented in docs/changes.html
  +  Highlights include:
  +
  +  * Database connection pooling
  +  * Numerous bugfixes, including better Servlet 2.0 compatibility
  +  * Increased performance for heavy load conditions
  +  * Also increased speed for some XSP pages which include complex Nodes
  +  * New ESQL logicsheet allowing easy post-processing of resultsets in XSP
  +  * Improved documentation, with new expanded FAQ
  +  * More installation instructions for more different servlet engines
  +  * Experimental FP taglib for form-handling and other tasks
  +  * Jikes support for faster XSP page compilation
   
   
     Licensing and legal issues
  
  
  
  1.33      +3 -6      xml-cocoon/todo.xml
  
  Index: todo.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/todo.xml,v
  retrieving revision 1.32
  retrieving revision 1.33
  diff -u -r1.32 -r1.33
  --- todo.xml	2000/09/19 23:01:36	1.32
  +++ todo.xml	2000/09/22 22:56:47	1.33
  @@ -3,7 +3,7 @@
   <!DOCTYPE todo SYSTEM "./xdocs/dtd/todo-v10.dtd">
   
   <!--
  -  $Id: todo.xml,v 1.32 2000/09/19 23:01:36 greenrd Exp $
  +  $Id: todo.xml,v 1.33 2000/09/22 22:56:47 greenrd Exp $
   -->
   
   <todo title="Things To Do for Cocoon 1.x">
  @@ -23,6 +23,9 @@
    </actions>
   
    <actions priority="medium">
  +  <action context="code">
  +   Fix remaining caching bugs. Cleanup caching code, which is messy.
  +  </action>
     <action context="code" assigned-to="RDG">
      Fix stylesheet-chaining bug.
     </action>
  @@ -41,12 +44,6 @@
     <action context="code" assigned-to="RDG">
      Class auto-reloading for XSP pages
      (code written; just needs to be merged in and documented.)
  -  </action>
  - </actions>
  -
  - <actions priority="low">
  -  <action context="code">
  -   Fix remaining caching bugs. Cleanup caching code, which is messy.
     </action>
    </actions>
   
  
  
  
  1.11      +12 -2     xml-cocoon/skins/xml.apache.org/stylesheets/document2html.xsl
  
  Index: document2html.xsl
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/skins/xml.apache.org/stylesheets/document2html.xsl,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- document2html.xsl	2000/09/19 23:01:38	1.10
  +++ document2html.xsl	2000/09/22 22:56:49	1.11
  @@ -459,17 +459,27 @@
      <a href="{@href}"><xsl:apply-templates/></a>
    </xsl:template>
   
  + <!-- hacky hacky! :-) -->
    <xsl:template match="connect">
  +
  +  <xsl:variable name="cref"><xsl:value-of select="@href"/></xsl:variable>
  +
  +  <!-- look up the soft link in the index to try and convert it to a hard link -->
  +  <xsl:variable name="converted"><xsl:value-of select="document('sbk:/sources/book.xml')//*[@source=$cref]/@id"/></xsl:variable>
  +
     <xsl:variable name="htmlref"><xsl:choose>
  -    <xsl:when test="substring(@href,string-length(@href)-4)='.xml'">
  +    <xsl:when test="$converted"><xsl:value-of select="$converted"/>.html</xsl:when>
  +    <xsl:when test="substring(@href,string-length(@href)-3)='.xml'">
  +     <!-- if not in the index, guess -->
        <xsl:value-of select="substring(@href,1,string-length(@href)-4)"/>.html
       </xsl:when>
       <xsl:otherwise>
  +     <!-- give up -->
        <xsl:value-of select="@href"/>
       </xsl:otherwise>
      </xsl:choose></xsl:variable>
   
  -  <a href="{$htmlref}#{@anchor}"><xsl:apply-templates/></a>
  +  <a href="{$htmlref}"><xsl:apply-templates/></a>
    </xsl:template>
   
    <xsl:template match="jump">
  
  
  
  1.4       +47 -41    xml-cocoon/xdocs/connection-pool.xml
  
  Index: connection-pool.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/xdocs/connection-pool.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- connection-pool.xml	2000/07/21 20:08:53	1.3
  +++ connection-pool.xml	2000/09/22 22:56:51	1.4
  @@ -4,7 +4,7 @@
   
   <document>
    <header>
  -  <title>Installing Cocoon Pool</title>
  +  <title>Using DB Connection Pooling</title>
     <authors>
      <person name="Brian Millett" email="bpm@ec-group.com"/>
     </authors>
  @@ -16,21 +16,21 @@
   
     <p>
      In the <code>/lib</code> directory you'll find the <code>turbine-pool.jar</code>
  -   jar package that contains the Turbine Connection Pool binary files.
  +   jar package that contains the Turbine Connection Pool binary files
  +   (a new addition to Cocoon in version 1.8).
      While this package may not be the most up-to-date version, it is
      guaranteed and tested to work properly with Cocoon so, we suggest that you
  -   use it. Note, however, that it was redistributed untouched from
  -   its original distribution.
  +   use it.
     </p>
    </s1>
   
    <s1 title="Installing Turbine Connection Pool">
   
  -  <s2 title="Installing Cocoon on Apache JServ">
  +  <s2 title="Installing on Apache JServ">
      <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
  +    On JServ, it is necessary to make sure that the new turbine-pool.jar is visible to
Java.
  +    This implies adding
  +    the following to the servlet engine classpath by adding a line
       to your <code>jserv.properties</code> file for the connection pool jar
package.
      </p>
   
  @@ -44,6 +44,10 @@
   wrapper.classpath=/usr/local/java/cocoon/lib/turbine-pool.jar
   </source>
   
  +   <p>Please also read the next section.</p>
  +  </s2>
  +
  +  <s2 title="Generic Installation for All Servlet Engines">
        <p>To use the pool, you need to have the appropriate properties defined
           in your <em>cocoon.properties</em> file. The important ones are listed
below.
           This is an example of creating a default pool for use with Oracle. Currently
  @@ -79,8 +83,8 @@
   
        <p> The <strong>default</strong> is by convention the default connection
used
            by the Turbine Connection Pool.  To define a Named connection, add new entries
  -         with the word "default" replaced with the name you want.  Here is an example 
  -         for defining a connection to a MySQL database called "helpdesk":</p>
  +         with the word "default" replaced with the name you want.  Here is an example
  +         for defining a connection to an Oracle database called "helpdesk":</p>
        <source>
           processor.xsp.pool.database.helpdesk.driver=oracle.jdbc.driver.OracleDriver
           processor.xsp.pool.database.helpdesk.url=jdbc:oracle:thin:@localhost:1521:ORCL
  @@ -99,26 +103,26 @@
           the various connection interfaces javadoc and drivers to find out the appropriate
           strings to use.</p>
   
  -   <p>
  -   </p>
  -
      </s2>
  +
    </s1>
  - <s1 title="Using Turbine Connection Pool in your code">
  + <s1 title="Using Turbine Connection Pool">
       <p>This section is to describe how you can use the Turbine connection pool
  -    in your own code. To demonstrate this, I'll show an example how I modified
  -    Ricardo Rocha's excellent example XSQL. this is some of the code that he
  +    in your own code. (At the time of writing, in Cocoon only the SQL taglibs
  +    use connection pooling - another good reason to use the SQL taglibs!)
  +    To demonstrate this, I'll show an example of how I modified
  +    Ricardo Rocha's excellent example XSQL. This is some of the code that he
       had before:</p>
  -    
  +
     <source><![CDATA[
       import java.sql.*;
       import java.util.*;
       import org.w3c.dom.*;
       import DBConnectionManager;
  -    
  +
       public class XSQL {
         static DBConnectionManager manager = DBConnectionManager.getInstance();
  -    
  +
         public static Element executeQuery(
           String connectionName,
           String statementId,
  @@ -128,17 +132,17 @@
           throws SQLException
         {
           Connection connection = null;
  -        
  +
           try {
             connection = manager.getConnection(connectionName);
             Statement statement = connection.createStatement();
             ResultSet resultSet = statement.executeQuery(statementText);
             ResultSetMetaData metaData = resultSet.getMetaData();
             int columnCount = metaData.getColumnCount();
  -          
  +
             Element rowSet = factory.createElement("xsql:rowset");
             rowSet.setAttribute("id", statementId);
  -    
  +
             for (int i = 0; resultSet.next(); i++) {
               Element row = factory.createElement("xsql:row");
               row.setAttribute("sequence", String.valueOf(i + 1));
  @@ -146,12 +150,12 @@
       
               for (int j = 0; j &lt; columnCount; j++) {
                 String value = resultSet.getString(j + 1);
  -    
  +
                 Element element = factory.createElement(
                  metaData.getColumnLabel(j + 1).toLowerCase()
                 );
                 row.appendChild(element);
  -    
  +
                 if (value != null) {
                   element.appendChild(
                     factory.createTextNode(value)
  @@ -159,10 +163,10 @@
                 }
               }
             }
  -    
  +
             resultSet.close();
             statement.close();
  -    
  +
             return rowSet;
           } catch (SQLException e) {
             throw(new SQLException(statementText));
  @@ -172,20 +176,20 @@
             }
           }
         }
  -    
  +
       }
       ]]></source>
  -    <p>Now this is the code modified to use the Turbine conncection pool:</p>
  -    
  +    <p>Now this is the code modified to use the Turbine connection pool:</p>
  +
     <source><![CDATA[
       import java.sql.*;
       import java.util.*;
       import org.w3c.dom.*;
       import DBConnectionManager;
  -    
  +
       public class XSQL {
           static DBBroker pool = DBBroker.getInstance();       // <---- Pool code!
  -        
  +
           public static Element executeQuery(
           String connectionName,
           String statementId,
  @@ -203,23 +207,23 @@
             ResultSet resultSet = statement.executeQuery(statementText);
             ResultSetMetaData metaData = resultSet.getMetaData();
             int columnCount = metaData.getColumnCount();
  -          
  +
             Element rowSet = factory.createElement("xsql:rowset");
             rowSet.setAttribute("id", statementId);
  -    
  +
             for (int i = 0; resultSet.next(); i++) {
               Element row = factory.createElement("xsql:row");
               row.setAttribute("sequence", String.valueOf(i + 1));
               rowSet.appendChild(row);
  -    
  +
               for (int j = 0; j &lt; columnCount; j++) {
                 String value = resultSet.getString(j + 1);
  -    
  +
                 Element element = factory.createElement(
                   metaData.getColumnLabel(j + 1).toLowerCase()
                 );
                 row.appendChild(element);
  -    
  +
                 if (value != null) {
                   element.appendChild(
                     factory.createTextNode(value)
  @@ -227,10 +231,10 @@
                 }
               }
             }
  -    
  +
             resultSet.close();
             statement.close();
  -    
  +
             return rowSet;
           } catch (SQLException e) {
             throw(new SQLException(statementText));
  @@ -240,12 +244,14 @@
             }
           }
         }
  -    
  +
       }
       ]]></source>
  +
       <p>Please see the <link href="http://java.apache.org/turbine/getting_started.html">getting
  -    started</link> documentation at the <link href="http://java.apache.org/turbine/">Turbine</link>
  -    homepage for more information about Turbine.
  +     started</link> documentation at the <link href="http://java.apache.org/turbine/">Turbine</link>
  +     homepage for more information about Turbine (a server-side framework which is
  +     the home of the connection pool code).
       </p>
     </s1>
   </body>
  
  
  
  1.16      +1 -0      xml-cocoon/xdocs/docs-book.xml
  
  Index: docs-book.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/xdocs/docs-book.xml,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -r1.15 -r1.16
  --- docs-book.xml	2000/09/19 23:01:41	1.15
  +++ docs-book.xml	2000/09/22 22:56:52	1.16
  @@ -36,6 +36,7 @@
   <separator/>
     <external label="Code Repository" href="http://xml.apache.org/websrc/index.cgi/xml-cocoon/"/>
     <external label="Dev Snapshots" href="http://xml.apache.org/from-cvs/xml-cocoon/"/>
  +  <page id="mail-lists" label="Mail Lists" source="mail-lists.xml"/>
     <external label="Mail Archive" href="http://mail-archives.apache.org/"/>
     <!-- <external label="Bug Database" href="http://xml.apache.org/bugs/"/> -->
   </book>
  
  
  
  1.18      +46 -17    xml-cocoon/xdocs/faq.xml
  
  Index: faq.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/xdocs/faq.xml,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -r1.17 -r1.18
  --- faq.xml	2000/09/19 23:01:41	1.17
  +++ faq.xml	2000/09/22 22:56:52	1.18
  @@ -10,12 +10,13 @@
     <question>I tried to access Cocoon.xml but it doesn't seem to exist.
      Where is it?</question>
     <answer>
  -   <p>Firstly, Cocoon.xml is not an actual file on the disk - it is a special
  -    "virtual" test page. Note that it is case-sensitive, so
  -    cocoon.xml won't work.</p>
  -
  -   <p>If the webserver returns "file not found" for Cocoon.xml, this indicates that
  -    you haven't installed Cocoon correctly. See the next question.</p>
  +   <p>Firstly, <code>Cocoon.xml</code> is not an actual file on the disk
- 
  +    it is a special "virtual" test page. Note that it is case-sensitive, so
  +    <code>cocoon.xml</code> won't work.</p>
  +
  +   <p>If the webserver returns "file not found" for <code>Cocoon.xml</code>,
  +    this indicates that you haven't installed Cocoon correctly. 
  +    See the next question.</p>
     </answer>
    </faq>
   
  @@ -96,6 +97,14 @@
     </answer>
    </faq>
   
  + <faq id="mac">
  +  <question>Why doesn't Cocoon work on my Mac?</question>
  +  <answer>
  +   <p>There is a long filename bug in some MRJs. Cocoon should work fine
  +   on Mac OS 9 or above with MRJ 2.2 or above.</p>
  +  </answer>
  + </faq>
  +
    <faq id="noant">
     <question>When I compile Cocoon on my system, I get a bunch of errors.
      What's wrong?</question>
  @@ -236,7 +245,7 @@
   
    <faq id="noclasspath">
     <question>I used xsp:include to import my classes, but it comes up
  -   with <em>Package "mypackage" not found in import</em> Why?</question>
  +   with <em>'Package "mypackage" not found in import'</em> Why?</question>
     <answer>
   
      <p>
  @@ -364,8 +373,8 @@
   
      <source><![CDATA[<?cocoon-format type="text/html/loose"?>]]></source>
   
  -   <p>in the source document (but make sure your stylesheet copies the PIs -
  -    see the question below),
  +   <p>in the source document (but make sure your stylesheet 
  +    <connect href="#lostpis">copies the PIs</connect> or this will disappear!),
       you indicate the page containing this processing instruction should be
       encoded and sent using the formatting properties contained in
       your <code>cocoon.properties</code>
  @@ -453,8 +462,15 @@
      ignore this, but IE won't, and will react to the MIME type and 
      trigger the correct plugin/application for that content.</p>
   
  -   <p>In the last resort, renaming all your xml files to end in .pdf should always
  -    work. Note that this is <em>not</em> a bug in Cocoon and is completely
outside
  +   <p>Russ Whyte has also developed a 
  +    <link href="http://archive.covalent.net/xml/cocoon-users/2000/09/0618.xml">
  +    simple servlet workaround</link> which should work for any browser;
  +    however this is slightly less efficient because it requires a "servlet chain".</p>
  +
  +   <p>In the last resort, renaming all your xml files to end in .pdf and 
  +    directing .pdf requests to Cocoon should always
  +    work (Cocoon doesn't care what filename it's given).
  +    Note that this is <em>not</em> a bug in Cocoon and is completely outside
       our control.</p>
   
      <note>There is a bug in MS Internet Explorer 5 which even ignores the 
  @@ -468,7 +484,7 @@
     <question>Is there a way to fake the requesting
      UserAgent from my browser? That would make testing easier.</question>
     <answer>
  -   <p>Yes - just append <code>?user-agent="xxx"</code> to your requested
URI and
  +   <p>Yes - just append <code>?user-agent=xxx</code> to your requested
URI and
       Cocoon will ignore the userAgent description that your browser is sending and
       use the one you specified instead.</p>
     </answer>
  @@ -487,11 +503,11 @@
       (thanks to James Vanetten for this list):</p>
   
      <ul>
  -    <li>jndi.jar</li>
  -    <li>ldap1_2_2/lib/ldap.jar</li>
  -    <li>ldap1_2_2/lib/providerutil.jar</li>
  -    <li>ldap1_2_2/lib/jaas.jar</li>
  -    <li>ldap1_2_2/lib/ldapbp.jar</li>
  +    <li><code>jndi.jar</code></li>
  +    <li><code>ldap1_2_2/lib/ldap.jar</code></li>
  +    <li><code>ldap1_2_2/lib/providerutil.jar</code></li>
  +    <li><code>ldap1_2_2/lib/jaas.jar</code></li>
  +    <li><code>ldap1_2_2/lib/ldapbp.jar</code></li>
      </ul>
   
      <note>If you built cocoon yourself, without the JNDI JAR on the classpath, you
will
  @@ -735,6 +751,19 @@
   </faqsection>
   
   <faqsection title="General">
  +
  + <faq id="ejbs">
  +  <question>How can EJBs be used with Cocoon</question>
  +  <answer>
  +   <p><em>(Thanks for Sebastien Sahuc for this answer.)</em> 
  +    Using EJB in Cocoon is just a matter of setting the servlet environment 
  +    to acts a a client EJB. So on one side you'll get your EJB server running 
  +    and listening for upcoming request, and on the other side you start your 
  +    Servlet Container with the right EJB client libraries so that whatever 
  +    servlet (or Cocoon code through XSP page for instance) you write can 
  +    contain EJB invocations.</p>
  +  </answer>
  + </faq>
   
    <faq id="cocoon2">
     <question>When can we expect to see the first proper release of Cocoon 2?</question>
  
  
  
  1.9       +3 -3      xml-cocoon/xdocs/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/xdocs/index.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- index.xml	2000/09/19 23:01:43	1.8
  +++ index.xml	2000/09/22 22:56:53	1.9
  @@ -169,10 +169,10 @@
     </p>
     <p>
      For direct participation, we suggest you to subscribe to the
  -   <link href="http://xml.apache.org/mail.html">Cocoon mailing lists</link>
  +   <connect href="mail-lists.xml">Cocoon mailing lists</connect>
      (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
  +   list archives), to checkout the <link href="http://xml.apache.org/websrc/index.cgi/xml-cocoon/">
  +   latest and greatest code</link> (which you find in the xml-cocoon module in
      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>
  
  
  
  1.24      +58 -5     xml-cocoon/xdocs/installing.xml
  
  Index: installing.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/xdocs/installing.xml,v
  retrieving revision 1.23
  retrieving revision 1.24
  diff -u -r1.23 -r1.24
  --- installing.xml	2000/09/19 23:01:44	1.23
  +++ installing.xml	2000/09/22 22:56:53	1.24
  @@ -180,8 +180,7 @@
   
      <p>
       If you haven't already got the Actions module compiled in to Apache
  -    (<strong>note - this is compiled in by default in standard installs
  -    </strong>),
  +    (<strong>note - this is compiled in by default in standard installs</strong>),
       you will need to have the following line uncommented in your
       <code>httpd.conf</code> or Apache will not be able to start:
      </p>
  @@ -451,9 +450,12 @@
     have to be willing to live without hot redeployment).</p>
   
     <p>To disable the WebLogic class loader, put your application classes,
  -  the Cocoon jars and _all_ of the WebLogic Server stuff into the Java
  -  CLASSPATH add -Dweblogic.system.disableWeblogicClassPath=true to the
  -  Java command at the end of you WebLogic start script.</p>
  +  the Cocoon jars and <em>all</em> of the WebLogic Server stuff into the Java
  +  CLASSPATH, and add</p>
  +
  +  <source>-Dweblogic.system.disableWeblogicClassPath=true</source>
  +
  +  <p>to the Java command at the end of you WebLogic start script.</p>
    </s3>
   
    <p>The above will also work for installing Cocoon in the BEA WebLogic
  @@ -613,6 +615,12 @@
      <th>JVM</th>
     </tr>
     <tr>
  +   <td>Debian Potato or Woody</td>
  +   <td>Apache 1.3.12</td>
  +   <td>JServ 1.1.2</td>
  +   <td>IBM JDK 1.1.8 or 1.3</td>
  +  </tr>
  +  <tr>
      <td>RedHat Linux 6.0</td>
      <td>Apache 1.3.9</td>
      <td>Apache JServ 1.0</td>
  @@ -649,12 +657,30 @@
      <td>IBM JDK 1.1.8</td>
     </tr>
     <tr>
  +   <td>RedHat Linux 6.1</td>
  +   <td>Apache 1.3.12-2</td>
  +   <td>Jserv 1.1.2-2</td>
  +   <td>JDK 1.2.2_006</td>
  +  </tr>
  +  <tr>
      <td>RedHat Linux 6.2 (i686)</td>
      <td>Apache 1.3.12 + mod_ssl 2.6.5</td>
      <td>JRun 2.3.3</td>
      <td>Sun JDK 1.2.2</td>
     </tr>
     <tr>
  +   <td>RedHat Linux 6.2</td>
  +   <td>Apache 1.3.12-2</td>
  +   <td>Tomcat 3.1</td>
  +   <td>JDK 1.2.2_006</td>
  +  </tr>
  +  <tr>
  +   <td>RedHat Linux 6.2 (i686)</td>
  +   <td>Apache 1.3.12</td>
  +   <td>Resin 1.2.b1</td>
  +   <td>Sun JDK 1.2.2</td>
  +  </tr>
  +  <tr>
      <td>SuSE 6.3 Linux</td>
      <td>Apache 1.3.9</td>
      <td>Apache JServ 1.1</td>
  @@ -725,6 +751,12 @@
      <td>Sun JDK 1.2.2</td>
     </tr>
     <tr>
  +   <td>Windows NT 4.0 SP5</td>
  +   <td>IIS 4.0</td>
  +   <td>Websphere 3.5 Enterprise</td>
  +   <td>IBM JDK 1.2.2</td>
  +  </tr>
  +  <tr>
      <td>Windows NT 4.0 SP6a</td>
      <td>Apache 1.3.11</td>
      <td>Apache JServ 1.1</td>
  @@ -743,12 +775,22 @@
      <td>Sun JDK 1.3</td>
     </tr>
     <tr>
  +   <td>Windows 2000 Advanced Server</td>
  +   <td colspan="2">Tomcat 3.1</td>
  +   <td>JDK 1.3</td>
  +  </tr>
  +  <tr>
      <td>MacOS 8.5+</td>
      <td colspan="2">Resin 1.1b</td>
      <td>MRJ 2.2</td>
     </tr>
     <tr>
      <td>MacOS 8.6</td>
  +   <td colspan="2">Tomcat 3.1</td>
  +   <td>MRJ 2.2.2</td>
  +  </tr>
  +  <tr>
  +   <td>MacOS 8.6</td>
      <td>WebSTAR 4.0</td>
      <td>JRun 2.3</td>
      <td>MrJ 2.1.4</td>
  @@ -784,6 +826,11 @@
      <td>Sun JDK 1.3 Beta Refresh</td>
     </tr>
     <tr>
  +   <td>Solaris 8 (x86)</td>
  +   <td colspan="2">Resin 1.2.b1</td>
  +   <td>JDK 1.3 beta</td>
  +  </tr>
  +  <tr>
      <td>FreeBSD 3.4</td>
      <td>Apache 1.3.9</td>
      <td>Apache JServ 1.0</td>
  @@ -793,6 +840,12 @@
      <td>FreeBSD 3.4-STABLE with linux_base-6.1 for linux-emulation</td>
      <td colspan="2">Jetty Java HTTP Server v2.3.3</td>
      <td>Blackdown jdk-1.2.2-RC4-linux-i386-glibc</td>
  +  </tr>
  +  <tr>
  +   <td>FreeBSD 4.1 (RELEASE)</td>
  +   <td>Apache 1.3.12</td>
  +   <td>Jserv 1.1.2</td>
  +   <td>Linux JDK 1.2.2</td>
     </tr>
     <tr>
      <td>SCO OpenServer 5</td>
  
  
  
  1.3       +3 -3      xml-cocoon/xdocs/infrastructure.xml
  
  Index: infrastructure.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/xdocs/infrastructure.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- infrastructure.xml	2000/04/18 12:53:34	1.2
  +++ infrastructure.xml	2000/09/22 22:56:54	1.3
  @@ -56,7 +56,7 @@
   
   <p>Once installed on a web server such as Site Server, Apache or
   Netscape. Cocoon doesn't require any user intervention. It is there
  -and usable for content publishing. Only when creating custom XML
  +and usable for content publishing. Only when creating a custom XML
   processor does one need to touch Cocoon itself.</p>
   
   <p>Cocoon offers transparent services with its API available through a
  @@ -115,8 +115,8 @@
   processing that might be too time consuming on runtime scenarios:
   automatic image generation, flow generation by directory analysis,
   etc. An example of an offline scenario can be seen at Cocoon's site
  -(<link href="http://xml.apache.org/cocoon">
  -http://xml.apache.org/cocoon</link>). On that site, the menus and headers
  +(<link href="http://xml.apache.org/cocoon/">http://xml.apache.org/cocoon</link>).
  +On that site, the menus and headers
   are automatically generated by processing XML content files, this
   allows for a more professional look and feel, yet it doesn't require
   an artist each time a label changes.</p>
  
  
  
  1.17      +1 -0      xml-cocoon/xdocs/site-book.xml
  
  Index: site-book.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/xdocs/site-book.xml,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -r1.16 -r1.17
  --- site-book.xml	2000/09/19 23:01:45	1.16
  +++ site-book.xml	2000/09/22 22:56:54	1.17
  @@ -38,6 +38,7 @@
   <separator/>
     <external label="Code Repository" href="http://xml.apache.org/websrc/index.cgi/xml-cocoon/"/>
     <external label="Dev Snapshots" href="http://xml.apache.org/from-cvs/xml-cocoon/"/>
  +  <page id="mail-lists" label="Mail Lists" source="mail-lists.xml"/>
     <external label="Mail Archive" href="http://mail-archives.apache.org/"/>
     <!-- <external label="Bug Database" href="http://xml.apache.org/bugs/"/> -->
   </book>
  
  
  
  1.1                  xml-cocoon/xdocs/mail-lists.xml
  
  Index: mail-lists.xml
  ===================================================================
  <?xml version="1.0"?>
  
  <!DOCTYPE document SYSTEM "./dtd/document-v10.dtd">
  
  <document>
   <header>
    <title>Mailing Lists</title>
    <authors>
     <person name="Robin Green" email="greenrd@hotmail.com"/>
    </authors>
   </header>
  
   <body>
    <s1 title="Important Notice">
  
     <p><strong>IMPORTANT: Before posting a question or problem to any mailing
list,
      </strong>please first look at the <connect href="faq.xml">FAQs</connect>
      and the <link href="http://mail-archives.apache.org/">mailing list
      archives</link> to avoid asking a question which has already been
      asked and answered dozens of times before!
     </p>
    </s1>
  
    <s1 title="Cocoon Users">
     <p><link href="mailto:cocoon-users-subscribe@xml.apache.org">Subscribe</link>
        <link href="mailto:cocoon-users-unsubscribe@xml.apache.org">Unsubscribe</link>
     </p>
  
     <p>The general Cocoon list, for problems, bug reports, asking for advice on how
      best to implement a site, comparisons with other XML frameworks, etc.
      But don't forget to look in the FAQ first, please!</p>
  
     <p>If you would like to make commercial solicitations, please ask permission from
       the list moderator first.</p>
  
     <note>This list is moderated, so the first time you post, there will be a
      delay before your post is reviewed and accepted. This is to prevent spam.</note>
    </s1>
  
    <s1 title="Cocoon Dev">
     <p><link href="mailto:cocoon-dev-subscribe@xml.apache.org">Subscribe</link>
        <link href="mailto:cocoon-dev-unsubscribe@xml.apache.org">Unsubscribe</link>
     </p>
  
     <p>This list is for developers <strong>working on</strong> or wanting
to work on
      Cocoon itself (not developers merely working <strong>with</strong> Cocoon),
      for code patches to Cocoon to be posted (please use <code>diff -u</code>
format),
      and for general Cocoon 2 questions.</p>
  
     <p>Note this is <strong>NOT</strong> for general Cocoon 1 questions
like "Why
      isn't Cocoon working on my machine?" - 
      please ask those sorts of questions cocoon users (after reading the
      FAQ first, of course).</p>
  
     <note>This list is moderated, so the first time you post, there will be a
      delay before your post is reviewed and accepted. This is to prevent spam.</note>
    </s1>
  
    <s1 title="Cocoon Cvs">
     <p><link href="mailto:cocoon-cvs-subscribe@xml.apache.org">Subscribe</link>
        <link href="mailto:cocoon-cvs-unsubscribe@xml.apache.org">Unsubscribe</link>
     </p>
  
     <p>This <strong>read-only</strong> list sends out notification messages
detailing
      any change made to the CVS repository where all the source code and libraries
      are stored for development purposes. The average user probably doesn't need to
      subscribe to this list.</p>
  
    </s1>
  
    <s1 title="Related Mailing Lists">
     <ul>
      <li><link href="http://www.mulberrytech.com/xsl/">Mulberrytech XSL list</link>
-
        more appropriate than Cocoon Users for general XSL questions.</li>
      <li><link href="http://xml.apache.org/mail.html">XML Apache Projects</link>
-
        list of mailing lists for all the projects on xml.apache.org.</li>
      <li>Some servlet engines have their own mailing lists for servlet-engine
       configuration questions, such as
       <link href="mailto:tomcat-user-subscribe">tomcat-user</link> (note it is
"user"
       and not "users").</li>
     </ul>
    </s1>
   </body>
  </document>
  
  
  

Mime
View raw message