xml-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From stef...@locus.apache.org
Subject cvs commit: xml-site/sources/cocoon changes-sbk.xml cocoon2-sbk.xml dcpprocessor-sbk.xml dynamic-sbk.xml faq-sbk.xml guide-sbk.xml index-sbk.xml installing-sbk.xml javadoc-sbk.xml license-sbk.xml sqlprocessor-sbk.xml technologies-sbk.xml todo-sbk.xml WD-xsp-sbk.xml readme.xml
Date Sat, 11 Dec 1999 14:24:50 GMT
stefano     99/12/11 06:24:50

  Modified:    sources/cocoon changes-sbk.xml cocoon2-sbk.xml
                        dcpprocessor-sbk.xml dynamic-sbk.xml faq-sbk.xml
                        guide-sbk.xml index-sbk.xml installing-sbk.xml
                        javadoc-sbk.xml license-sbk.xml
                        sqlprocessor-sbk.xml technologies-sbk.xml
                        todo-sbk.xml WD-xsp-sbk.xml
  Removed:     sources/cocoon readme.xml
  Log:
  updated cocoon site
  
  Revision  Changes    Path
  1.2       +24 -14    xml-site/sources/cocoon/changes-sbk.xml
  
  Index: changes-sbk.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/cocoon/changes-sbk.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- changes-sbk.xml	1999/12/03 00:14:03	1.1
  +++ changes-sbk.xml	1999/12/11 14:24:48	1.2
  @@ -1,3 +1,4 @@
  +<?xml version="1.0" encoding="UTF-8"?>
   <s1 title="Changes"><s2 title="Main Developers"><ul><li><anchor
name="SM"/><jump href="mailto:stefano@apache.org">Stefano Mazzocchi</jump></li><li><anchor
name="DB"/><jump href="mailto:balld@webslingerZ.com">Donald Ball</jump></li><li><anchor
name="RR"/><jump href="mailto:rrocha@plenix.org">Ricardo Rocha</jump></li></ul></s2>
     
       
  @@ -6,6 +7,21 @@
     
   
    <s2 title="Cocoon 1.6-dev (not yet released)"><ul>
  +  <li><img alt="fix" src="images/fix.jpg"/>
  +  	Added dummy methods to EngineWrapper for JSDK 2.2 compatibility
  +  (<jump href="#DB">DB</jump>) Thanks to <jump href="mailto:martinguitar@hotmail.com">Brett
McLaughlin</jump>.</li>
  +  <li><img alt="add" src="images/add.jpg"/>
  +  	Added ProducerFromMap as a sitemap primer.
  +  (<jump href="#DB">DB</jump>)</li>
  +  <li><img alt="add" src="images/add.jpg"/>
  +  	Added Tomcat installation instructions.
  +  (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:bmclaugh@algx.net">Brett
McLaughlin</jump>.</li>
  +  <li><img alt="update" src="images/update.jpg"/>
  +  	Moved a few things around in ColumnFormatter so that it's possible for columns to be
formatted as more than simply a text node (e.g. embedded HTML). Also added a little formatter
that can transform \n into &lt;br&gt; for text and varchar columns.
  +  (<jump href="#DB">DB</jump>)</li>
  +  <li><img alt="add" src="images/add.jpg"/>
  +  	Added new classes to SQLProcessor to do column-specific date formatting.
  +  (<jump href="#DB">DB</jump>) Thanks to <jump href="mailto:ed@waterfall.freeserve.co.uk">Ed
Ward</jump>.</li>
     <li><img alt="add" src="images/add.jpg"/>
       Add new producer for POST document processing, also useful for use of 
       Cocoon as a module (see EngineWrapper).
  @@ -19,12 +35,6 @@
     <li><img alt="add" src="images/add.jpg"/>
       Added Documentation DTD.
     (<jump href="#SM">SM</jump>)</li>
  -  <li><img alt="add" src="images/add.jpg"/>
  -    Added Documentation DTD.
  -  (<jump href="#SM">SM</jump>)</li>
  -  <li><img alt="update" src="images/update.jpg"/>
  -    Moved "examples/" under "samples/" for global xml.apache.org pattern.
  -  (<jump href="#SM">SM</jump>)</li>
     <li><img alt="update" src="images/update.jpg"/>
       Moved "examples/" under "samples/" for global xml.apache.org pattern.
     (<jump href="#SM">SM</jump>)</li>
  @@ -79,7 +89,7 @@
       outside. This was breaking the WML formatter.
     (<jump href="#SM">SM</jump>)</li>
     <li><img alt="fix" src="images/fix.jpg"/>
  -    Patched XSL:P to support &lt;&lt;xsl:processing-instruction&gt;&gt;
instead of &lt;&lt;xsl:pi&gt;&gt; which is now deprecated. 
  +    Patched XSL:P to support &lt;xsl:processing-instruction&gt; instead of &lt;xsl:pi&gt;
which is now deprecated. 
       This makes XSL:P a hybrid between XSLT revisions but it's easier this way than to create
two sets
       of examples that work with latest and oldest releases of XSLT. Hopefully XSLT will
standardize soon.
     (<jump href="#SM">SM</jump>)</li>
  @@ -118,7 +128,7 @@
       Added WML formatter.
     (<jump href="#SM">SM</jump>)</li>
     <li><img alt="add" src="images/add.jpg"/>
  -    Added the ability to ""mount"" the Cocoon status to a configurable URL.
  +    Added the ability to "mount" the Cocoon status to a configurable URL.
     (<jump href="#SM">SM</jump>)</li>
     <li><img alt="add" src="images/add.jpg"/>
       Added the ability to hide Cocoon status for security reasons.
  @@ -146,7 +156,7 @@
       Updated the examples to reflect the changes.
     (<jump href="#SM">SM</jump>)</li>
     <li><img alt="update" src="images/update.jpg"/>
  -    Changed Cocoon illegal PIs from &lt;&lt;?cocon:xxx?&gt;&gt; to &lt;&lt;?cocoon-xxx?&gt;&gt;.
  +    Changed Cocoon illegal PIs from &lt;?cocon:xxx?&gt; to &lt;?cocoon-xxx?&gt;.
     (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:tbray@textuality.com">Tim
Bray</jump>.</li>
   </ul></s2>
   
  @@ -169,8 +179,8 @@
       of scanning the whole file.
     (<jump href="#SM">SM</jump>)</li>
     <li><img alt="update" src="images/update.jpg"/>
  -    Updated the cocoon processing instructions that drive the reaction: &lt;&lt;?cocoon:process?&gt;&gt;
  -    drives the processing reaction, &lt;&lt;?cocoon.format?&gt;&gt; indicates
the
  +    Updated the cocoon processing instructions that drive the reaction: &lt;?cocoon:process?&gt;
  +    drives the processing reaction, &lt;?cocoon.format?&gt; indicates the
       formatter used to end processing and format the document.
     (<jump href="#SM">SM</jump>)</li>
     <li><img alt="remove" src="images/remove.jpg"/>
  @@ -302,7 +312,7 @@
       Fixed the final Vector.toString() problem in JDK 1.1 compilation.
     (<jump href="#SM">SM</jump>)</li>
     <li><img alt="fix" src="images/fix.jpg"/>
  -    Fixed the ""verify error"" by using Jikes compiler for distribution.
  +    Fixed the "verify error" by using Jikes compiler for distribution.
     (<jump href="#SM">SM</jump>)</li>
     <li><img alt="update" src="images/update.jpg"/>
       Cleaned up documentation and added some entries in the FAQ.
  @@ -367,8 +377,8 @@
   
   <s2 title="Cocoon 1.1 (March 25 1999)"><ul>
    <li><img alt="update" src="images/update.jpg"/>
  -  Changed the stylesheet mapping processing instruction from illegal ""xml:stylesheet""
  -  to standard ""xml-stylesheet"".
  +  Changed the stylesheet mapping processing instruction from illegal "xml:stylesheet"
  +  to standard "xml-stylesheet".
    (<jump href="#SM">SM</jump>)</li>
    <li><img alt="add" src="images/add.jpg"/>
     Created Cocoon logo.
  
  
  
  1.2       +7 -6      xml-site/sources/cocoon/cocoon2-sbk.xml
  
  Index: cocoon2-sbk.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/cocoon/cocoon2-sbk.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- cocoon2-sbk.xml	1999/12/03 00:14:03	1.1
  +++ cocoon2-sbk.xml	1999/12/11 14:24:48	1.2
  @@ -1,3 +1,4 @@
  +<?xml version="1.0" encoding="UTF-8"?>
   <s1 title="Cocoon 2">
    
   
  @@ -25,7 +26,7 @@
   
    <s2 title="Passive APIs vs. Active APIs">
     <p>Web serving environments must be fast and scalable to be
  -  useful. Cocoon1 was born as a ""proof of concept"" rather than a
  +  useful. Cocoon1 was born as a "proof of concept" rather than a
     production software and had significant design restrictions based mainly on
     the availability of freely redistributable tools. Other issues were lack of
     detailed knowledge on the APIs available as well as underestimation of the
  @@ -36,8 +37,8 @@
     API which is a <ref>passive</ref> API and was intended mainly for client
side
     operation. This is mainly due to the fact that most (if not all!) DOM
     implementations require the document to reside in memory. While this is
  -  practical for small documents and thus good for the ""proof of
  -  concept"" stage, it is now considered a main design constraint for Cocoon
  +  practical for small documents and thus good for the "proof of
  +  concept" stage, it is now considered a main design constraint for Cocoon
     scalability.</p>
     
     <p>Since the goal of Cocoon2 is the ability to process
  @@ -155,8 +156,8 @@
     shape suitable to replace current high-structure web site management
     models.</p>
     
  -  <p>The model that Cocoon2 adopts is the ""pyramid model of
  -  web contracts"" which is outlined in the picture below</p>
  +  <p>The model that Cocoon2 adopts is the "pyramid model of
  +  web contracts" which is outlined in the picture below</p>
     
     <p><img alt="The Cocoon2 Pyramid Model of Contracts" src="images/pyramid-model.gif"/></p>
     
  @@ -181,7 +182,7 @@
       
       <li><em>Style</em> - 
         the people responsible for information
  -      presentation, look &amp;&amp; feel, site graphics and its maintenance.
  +      presentation, look &amp; feel, site graphics and its maintenance.
       </li>
       
     </ul>
  
  
  
  1.2       +1 -0      xml-site/sources/cocoon/dcpprocessor-sbk.xml
  
  Index: dcpprocessor-sbk.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/cocoon/dcpprocessor-sbk.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- dcpprocessor-sbk.xml	1999/12/03 00:14:03	1.1
  +++ dcpprocessor-sbk.xml	1999/12/11 14:24:48	1.2
  @@ -1,3 +1,4 @@
  +<?xml version="1.0" encoding="UTF-8"?>
   <s1 title="DCPProcessor User Guide">
    
   
  
  
  
  1.2       +1 -0      xml-site/sources/cocoon/dynamic-sbk.xml
  
  Index: dynamic-sbk.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/cocoon/dynamic-sbk.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- dynamic-sbk.xml	1999/12/03 00:14:03	1.1
  +++ dynamic-sbk.xml	1999/12/11 14:24:48	1.2
  @@ -1,3 +1,4 @@
  +<?xml version="1.0" encoding="UTF-8"?>
   <s1 title="Dynamic XML in Cocoon">
    
    
  
  
  
  1.2       +14 -13    xml-site/sources/cocoon/faq-sbk.xml
  
  Index: faq-sbk.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/cocoon/faq-sbk.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- faq-sbk.xml	1999/12/03 00:14:03	1.1
  +++ faq-sbk.xml	1999/12/11 14:24:48	1.2
  @@ -1,3 +1,4 @@
  +<?xml version="1.0" encoding="UTF-8"?>
   <faqs>
   
   <faq title="How do I pipe my servlet output into Cocoon?">
  @@ -56,34 +57,34 @@
   </a>
   </faq>
   
  -<faq title="The XSL book I read says the correct way of indicating the XSL stylesheet
is by&#10;    using the XML processing instruction &#60;&#60;?xml:stylesheet?&#62;&#62;
while Cocoon is&#10;    using &#60;&#60;?xml-stylesheet?&#62;&#62;. Who
is right?&#10; ">
  +<faq title="The XSL book I read says the correct way of indicating the XSL stylesheet
is by&#10;    using the XML processing instruction &#60;?xml:stylesheet?&#62;
while Cocoon is&#10;    using &#60;?xml-stylesheet?&#62;. Who is right?&#10;
">
    <q>The XSL book I read says the correct way of indicating the XSL stylesheet is
by
  -    using the XML processing instruction <code>&lt;&lt;?xml:stylesheet?&gt;&gt;</code>
while Cocoon is
  -    using <code>&lt;&lt;?xml-stylesheet?&gt;&gt;</code>. Who
is right?
  +    using the XML processing instruction <code>&lt;?xml:stylesheet?&gt;</code>
while Cocoon is
  +    using <code>&lt;?xml-stylesheet?&gt;</code>. Who is right?
    </q>
    <a>
  -  <p>The PI <code>&lt;&lt;?xml:stylesheet type=""text/xsl"" href=""""?&gt;&gt;</code>
  +  <p>The PI <code>&lt;?xml:stylesheet type="text/xsl" href=""?&gt;</code>
     is the old method of associating a stylesheet with an XML document. Unfortunately, this
     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 
     <jump href="http://www.w3.org/TR/xml-stylesheet">http://www.w3.org/TR/xml-stylesheet</jump>
and
  -  clearly indicates that <code>&lt;&lt;?xml-stylesheet ...?&gt;&gt;</code>
is the proper way.</p>
  +  clearly indicates that <code>&lt;?xml-stylesheet ...?&gt;</code>
is the proper way.</p>
    </a>
   </faq>
   
  -<faq title="&#10;    I think that using Processing Instructions to &#34;&#34;chain&#34;&#34;&#10;
   document layers somehow violates the context separation since I would like&#10;   
to be able to place style sensible information in sessions or request&#10;    parameters.
What do you think about this?&#10; ">
  +<faq title="&#10;    I think that using Processing Instructions to &#34;chain&#34;&#10;
   document layers somehow violates the context separation since I would like&#10;   
to be able to place style sensible information in sessions or request&#10;    parameters.
What do you think about this?&#10; ">
    <q>
  -    I think that using Processing Instructions to ""chain""
  +    I think that using Processing Instructions to "chain"
       document layers somehow violates the context separation since I would like
       to be able to place style sensible information in sessions or request
       parameters. What do you think about this?
    </q>
    <a>
     <p>You are right, PI reaction breaks the context separation and it's, at the
  -    very end, the wrong approach. To follow a complete ""model, view,
  -    controller"" design pattern, one should be able to associate a different
  +    very end, the wrong approach. To follow a complete "model, view,
  +    controller" design pattern, one should be able to associate a different
       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 Cocoon2
  @@ -130,17 +131,17 @@
   </a>
   </faq>
   
  -<faq title="Why the name &#34;&#34;Cocoon&#34;&#34;?">
  - <q>Why the name ""Cocoon""?</q>
  +<faq title="Why the name &#34;Cocoon&#34;?">
  + <q>Why the name "Cocoon"?</q>
    <a>
     <p> (Cocoon's creator Stefano Mazzocchi answers): It's a pretty stupid reason and
a funny
     story: I spent my 1998 Xmas vacation with my girlfriend up on the Alps at her cottage.
One
     night I couldn't sleep, I went to watch some TV and finishing reading the XSL
     documentation I brought with me. Being a science fiction <ref>afficionado</ref>,
I found out
     that Ron Howard's movie Cocoon was on and I started watching it. The idea of the XSL
  -  rendering servlet stoke me like the alien ""cocoons"" in the pool stroke those old men
in the
  +  rendering servlet stoke me like the alien "cocoons" in the pool stroke those old men
in the
     movie and, while watching, I started paper-coding it right away. After a while the movie
  -  was over and the publishing framework designed. The name ""Cocoon"" seemed right
  +  was over and the publishing framework designed. The name "Cocoon" seemed right
     for the thing, meaning to be a way to bring new life to old ideas as well as to create
<ref>cocoons</ref>
     for such new ideas to become beautiful butterflies. :-)</p>
   </a>
  
  
  
  1.2       +5 -4      xml-site/sources/cocoon/guide-sbk.xml
  
  Index: guide-sbk.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/cocoon/guide-sbk.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- guide-sbk.xml	1999/12/03 00:14:03	1.1
  +++ guide-sbk.xml	1999/12/11 14:24:48	1.2
  @@ -1,3 +1,4 @@
  +<?xml version="1.0" encoding="UTF-8"?>
   <s1 title="User Guide">
    
   
  @@ -32,7 +33,7 @@
   me like I walk on water), and a couple of summer 
   interns that I had helping me on the project are 
   suddenly getting massively head-hunted by companies 
  -like AT&amp;&amp;T now that they can put XML and XSL on 
  +like AT&amp;T now that they can put XML and XSL on 
   their resumes.  In a word: Cocoon simply rocks!
   </source>
   </s2>
  @@ -67,7 +68,7 @@
     follow a <jump href="http://www.w3.org/TR/WD-xml-stylesheet">W3C recommendation</jump>
     and add the XML processing instruction to map a stylesheet to a document:</p>
     
  -  <source>&lt;&lt;xml-stylesheet href"hello.xsl" type="text/xsl"&gt;&gt;</source>
  +  <source>&lt;xml-stylesheet href"hello.xsl" type="text/xsl"&gt;</source>
     
     <p>Now that our content layer is done, we need to create a stylesheet to
     convert it to a format readable by our web clients. Since most available web
  @@ -291,11 +292,11 @@
     to the right processor or formatter. These processing instructions are:</p>
     
   <source>
  -&lt;&lt;?cocoon-process type="xxx"?&gt;&gt; for processing
  +&lt;?cocoon-process type="xxx"?&gt; for processing
   
         and
   
  -&lt;&lt;?cocoon-format type="yyy"?&gt;&gt; for formatting
  +&lt;?cocoon-format type="yyy"?&gt; for formatting
   </source>
   
     <p>These PIs are used to indicate the processing and formatting path that the
  
  
  
  1.2       +2 -1      xml-site/sources/cocoon/index-sbk.xml
  
  Index: index-sbk.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/cocoon/index-sbk.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- index-sbk.xml	1999/12/03 00:14:03	1.1
  +++ index-sbk.xml	1999/12/11 14:24:48	1.2
  @@ -1,3 +1,4 @@
  +<?xml version="1.0" encoding="UTF-8"?>
   <s1 title="Cocoon">
    
   
  @@ -143,7 +144,7 @@
      For direct participation, we suggest you to subscribe to the 
      <jump href="http://xml.apache.org/mail.html">Cocoon mail lists</jump> 
      (follow the link for information on how to subscribe and to access the mail 
  -   list archives), to checkout the <jump href="http://www.apache.com/cvsweb/index.cgi/cocoon/">
  +   list archives), to checkout the <jump href="http://xml.apache.org/websrc/cvsweb.cgi/xml-cocoon/">
      latest and greatest code</jump> (which you found in the xml-cocoon module in 
      the xml.apache.org CVS code repository), control the todo
      list and jump in. Document writers are usually the most wanted people so if
  
  
  
  1.2       +166 -46   xml-site/sources/cocoon/installing-sbk.xml
  
  Index: installing-sbk.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/cocoon/installing-sbk.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- installing-sbk.xml	1999/12/03 00:14:03	1.1
  +++ installing-sbk.xml	1999/12/11 14:24:48	1.2
  @@ -1,7 +1,9 @@
  +<?xml version="1.0" encoding="UTF-8"?>
   <s1 title="Installing Cocoon">
    
    
    
  + 
    <s2 title="System Requirements">
     <p>
      Cocoon requires the following systems to be already installed in your
  @@ -21,7 +23,6 @@
       is optional for command line operation.
      </li>
     </ul>
  -   
    </s2>
    
    <s2 title="Required Components">
  @@ -32,32 +33,60 @@
     </p>
     
     <p>
  -   Cocoon uses an XML parser and an XSLT processor has its basic components and
  -   uses the DOM API to access work with them. For this reason, you need both
  -   DOM-enabled XML parser and XSLT processor. Also, for complex formatting,
  -   Cocoon uses a formatting object renderer and a set of printing classes
  -   to send the page to the client.
  +   Here is a list of supported components with their minimum version required
  +   to operate with this version of Cocoon:
     </p>
     
  +  <table>
  +   
  +   
  +   
  +   
  +  </table>
  +   
  +  <table>
  +   
  +   
  +   
  +   
  +  </table>   
  +   
  +  <table>
  +   
  +   
  +   
  +  </table>   
  +  
  +  <note>
  +   Cocoon is strictly dependent on some printing classes contained into Xerces
  +   so, even if you use another parser, you should still keep Xerces visible
  +   to Cocoon.
  +  </note>
  +  
     <p>
  -   Being an Apache project, Cocoon focues on Apache technologies and comes
  -   configured to operate with Xerces, Xalan and FOP, but other DOM-aware 
  -   components are supported as well (see the <code>cocoon.properties</code>
  -   file for more information on other components supported).
  +   Being an Apache project, Cocoon focuses on Apache technologies but we are
  +   dedicated to support all compatible XML/XSL technologies and will welcome
  +   contributions to add support for other components not currently supported.
     </p>
     
     <p>
  -   For this reason, in order to work out of the box and have complete operation, 
  -   you need to download all three packages (Xerces-J, Xalan-J and FOP) from the
  -   <jump href="http://xml.apache.org/dist/">xml.apache.org</jump> distribution
  -   area. Once you have
  -   all three jar packages required and all other packages that may be required
  -   by these projects, go ahead and follow the instructions for your servlet
  -   engine.
  +   So this is your shopping list for components for complete operation:
     </p>
  - 
  +   
  +   <ul>
  +    <li>Apache Xerces (required for the formatting classes)</li>
  +    <li>Your favorite XML parser</li>
  +    <li>Your favorite XSLT processor</li>
  +    <li>Apache FOP (optional, unless you want PDF rendering)</li>
  +    <li>GNU Regexp (optional, unless you use <ref>ProducerFromMap</ref>)</li>
  +   </ul>
  +   
  +  <p>
  +   All right. Now that you have downloaded all the components you need, go on
  +   and jump to the installation instructions for your servlet engine.
  +  </p>
    </s2>
  -  
  + 
    <s2 title="Installing Cocoon">
     <p>
      Being Cocoon a servlet, you should be able to install it on every compliant
  @@ -75,47 +104,48 @@
      </p>
      
      <p>
  -    First thing to do is to make sure that the components needed by Cocoon (and
  -    explained in the above paragraphs) are visible. This implies adding this to
  -    the servlet engine classpath by adding a line like this in your 
  +    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 <ref>[path-to-jar]</ref> with the path to the jar file
and
  -    <ref>[jar-name]</ref> with the package file name.
  +    (after substituting <ref>[path-to-jar]</ref> with the path to the jar file
and
  +    <ref>[jar-name]</ref> with the package file name).
      </p>
       
      <source>wrapper.classpath=[path-to-jar]/[jar-name].jar</source>
      
      <p>
  -    <ref>Note:</ref> do not add the <code>cocoon.jar</code> package
here since
  -    this might corrupt it's normal operation. Here, you should add all the 
  -    required packages <ref>but</ref> Cocoon itself.
  +    Here is an example:
      </p>
      
  -   <p>
  -    At this point, you must tell the servlet engine to locate Cocoon (since
  -    you didn't do this in the step right above!). To do this, you should choose
  -    the servlet zone where you want Cocoon to reside. 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. Now add the 
  -    <code>cocoon.jar</code> package to your servlet zone by making sure
  -    a line like this is present in your zone property file.
  -   </p>
  +<source>
  +wrapper.classpath=/usr/local/java/lib/cocoon.jar
  +wrapper.classpath=/usr/local/java/lib/xerces.jar
  +wrapper.classpath=/usr/local/java/lib/xalan.jar
  +wrapper.classpath=/usr/local/java/lib/fop.jar
  +wrapper.classpath=/usr/local/java/lib/regexp.jar
  +</source>
      
  -   <source>repositories=...,[path-to-cocoon]/bin/cocoon.jar</source>
  +   <note>
  +    from this version of Cocoon the <code>Cocoon.jar</code> 
  +    package should be added to the servlet engine classpath as any other
  +    required package (as shown above).
  +   </note>
      
      <p>
  -    where ... stands for any other servlet repository the servlet zone already
  -    contains (or might be empty if no other repository is used by this zone) and
  -    <ref>[path-to-cocoon]</ref> is substitued by the actual path to the <code>
  -    cocoon.jar</code> file.
  +    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.
      </p>
      
      <p>
  -    Now the servlet engine knows where to locate the Cocoon servlet
  -    but Cocoon must need to know its configurations to be able to start. 
       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:
  +    <code>zone.properties</code> file (or each servlet zone file you want
  +    Cocoon to reside):
      </p>
      
      <source>servlet.org.apache.cocoon.Cocoon.initArgs=properties=[path-to-cocoon]/bin/cocoon.properties</source>
  @@ -142,16 +172,105 @@
       and <ref>/servlet/</ref> is the mount point of your servlet zone (and the
       above is the standard name for servlet mapping for Apache JServ).
      </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.
      </p>
  +   
  +   <p>
  +    <em>Note</em>: 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:
  +   </p>
  +   
  +<source>ApJServAction .xml1 /zone1/org.apache.cocoon.Cocoon
  +ApJServAction .xml2 /zone2/org.apache.cocoon.Cocoon</source>           
  +
  +   <p>
  +    where <ref>.xml1</ref> is handled by the Cocoon residing on <ref>zone1</ref>
  +    and <ref>.xml2</ref> is handled by the Cocoon residing on <ref>zone2</ref>
  +    which have different configurations and thus different behavior.
  +   </p>
     </s3>
     
     <s3 title="Installing Cocoon on Apache Tomcat">
  -   <p>Yet to be written! <ref>Volunteers welcome!</ref></p>
  +    <p>
  +     Tomcat has two basic methods of locating Java classes for the runtime environment.
  +     The first is the overall classpath that Tomcat uses to run, and this is the
  +     classpath provided to Java classes that use constructs such as
  +     <code>Class.forName().newInstance()</code>.  The second classpath is
  +     associated with a specific context, and is somewhat analagous to the
  +     servlet zones used in Apache JServ (see section above).
  +    </p>
  +
  +    <p>
  +     Because the Cocoon framework utilizes <code>Class.forName()</code> and
other
  +     dynamic instance handling techniques, the Cocoon classes need to have its
  +     classpath aware of the component classes used within the framework.  To do 
  +     this, take all the required components (see above) and put them in your 
  +     <ref>&lt;Tomcat-Root&gt;/lib</ref> directory.  This is the standard
location 
  +     for Tomcat core libraries. To ensure that Tomcat will use these, you need 
  +     to edit the Tomcat startup file.
  +    </p>
  +    
  +    <p>
  +     On Windows, this is <ref>&lt;Tomcat-Root&gt;/tomcat.bat</ref>
and on
  +     Unix, this is <ref>&lt;Tomcat-Root&gt;/tomcat.sh</ref>.  In this

  +     file you must add all the component jar files to Tomcat's classpath.
  +    </p>
  +
  +    <note>
  +     from this version of Cocoon the <code>Cocoon.jar</code> 
  +     package should be added to the servlet engine classpath as any other
  +     required package (as shown above).
  +    </note>
  +   
  +    <p>
  +     Next you need to tell your context where Cocoon can find it's properties 
  +     file, as well as to map Cocoon to XML document requests.
  +     Make sure you have a <ref>web.xml</ref> file in your context's
  +     <ref>WEB-INF</ref> directory.  This file specifies servlet mappings
  +     and initial arguments to servlets.  If you don't have this file, you can copy
  +     an example from <ref>&lt;Tomcat-Root&gt;/examples/WEB-INF</ref>
  +     directory.  You should add the following entries in that file:
  +    </p>
  +
  +<source>
  + &lt;servlet&gt;
  +  &lt;servlet-name&gt;org.apache.cocoon.Cocoon&lt;/servlet-name&gt;
  +  &lt;servlet-class&gt;org.apache.cocoon.Cocoon&lt;/servlet-class&gt;
  +  &lt;init-param&gt;
  +   &lt;param-name&gt;properties&lt;/param-name&gt;
  +   &lt;param-value&gt;
  +     [path-to-cocoon.properties]/cocoon.properties
  +   &lt;/param-value&gt;
  +  &lt;/init-param&gt;
  + &lt;/servlet&gt;
  + 
  + &lt;servlet-mapping&gt;
  +  &lt;servlet-name&gt;org.apache.cocoon.Cocoon&lt;/servlet-name&gt;
  +  &lt;url-pattern&gt;*.xml&lt;/url-pattern&gt;
  + &lt;/servlet-mapping&gt;
  +</source>
  +
  +    <p>
  +     Make sure you replaced the path to the Cocoon.properties file with the 
  +     actual location of that file on your system.
  +     Note that you should not need to change anything from the template
  +     properties file found in the distribution, but you must edit it for
  +     more complex operation. Please refer directly to the file that contains
  +     brief indications and comments on the different configurations, but you
  +     don't need to care about that at this point.
  +    </p>
  +
  +    <p>
  +     Everything should be configured fine. Restart Tomcat
  +     and try accessing the samples contained in the distribution to see
  +     Cocoon in action.
  +    </p>   
     </s3>
     
     <s3 title="Installing Cocoon on Allaire JRun">
  @@ -181,6 +300,7 @@
       <li>Windows 98 + MS Personal Web Server + ServletExec 2.2 + Sun JDK 1.2.1</li>
       <li>Windows NT 4.0 + IIS 4.0 + ServletExec 2.2 + Sun JDK 1.2.1</li>
       <li>Windows NT 4.0 + IIS 4.0 + JRun 2.3.3 + Sun JDK 1.2.1</li>
  +    <li>Windows NT 4.0 + Apache 1.3.9 + JRun 2.3.3 + Sun JDK 1.2.2</li>
       <li>MacOS 8.6 + WebSTAR 4.0 + JRun 2.3 + MrJ 2.1.4</li>
       <li>MacOS 8.6 + WebSTAR 4.0 + ServletExec 2.1 + Mrj 2.1.4</li>
       <li>SunOS Netria 5.6 + Apache 1.3.9 + Apache JServ 1.1b3 + Sun JDK 1.1.7</li>
  
  
  
  1.2       +7 -6      xml-site/sources/cocoon/javadoc-sbk.xml
  
  Index: javadoc-sbk.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/cocoon/javadoc-sbk.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- javadoc-sbk.xml	1999/12/03 00:14:03	1.1
  +++ javadoc-sbk.xml	1999/12/11 14:24:48	1.2
  @@ -1,3 +1,4 @@
  +<?xml version="1.0" encoding="UTF-8"?>
   <s1 title="Javadoc Documentation in XML">
    
   
  @@ -37,15 +38,15 @@
     </ul>
     <li>Some final formats we could produce are:</li>
     <ul>
  -    <li>javadoc.dtd ---&gt;&gt; javadoc_html.dtd ---&gt;&gt; HTML
(this would create a
  +    <li>javadoc.dtd ---&gt; javadoc_html.dtd ---&gt; HTML (this would create
a
           javadoc that looks like the current HTML javadoc standard).</li>
  -    <li>javadoc.dtd ---&gt;&gt; docBook.dtd (this would facilitate printed
  -        books based having heavy content about java API's. For example ""The
  -        JDBC API Tutorial and Reference: 2nd Edition"" could make heavy use
  +    <li>javadoc.dtd ---&gt; docBook.dtd (this would facilitate printed
  +        books based having heavy content about java API's. For example "The
  +        JDBC API Tutorial and Reference: 2nd Edition" could make heavy use
           of this.</li>
  -    <li>javadoc.dtd ---&gt;&gt; ebook.dtd (this would facilitate the electronic
  +    <li>javadoc.dtd ---&gt; ebook.dtd (this would facilitate the electronic
           version of documentation)</li>
  -    <li>javadoc.dtd ---&gt;&gt; ??? ---&gt;&gt; pdf</li>
  +    <li>javadoc.dtd ---&gt; ??? ---&gt; pdf</li>
     </ul>
     <li>Using this method we will then enhance the existing Cocoon documentation to
provide rich documentation
         using some subset of the above formats.</li>
  
  
  
  1.2       +1 -0      xml-site/sources/cocoon/license-sbk.xml
  
  Index: license-sbk.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/cocoon/license-sbk.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- license-sbk.xml	1999/12/03 00:14:03	1.1
  +++ license-sbk.xml	1999/12/11 14:24:48	1.2
  @@ -1,3 +1,4 @@
  +<?xml version="1.0" encoding="UTF-8"?>
   <s1 title="Cocoon Public License">
    
   
  
  
  
  1.2       +1 -0      xml-site/sources/cocoon/sqlprocessor-sbk.xml
  
  Index: sqlprocessor-sbk.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/cocoon/sqlprocessor-sbk.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- sqlprocessor-sbk.xml	1999/12/03 00:14:03	1.1
  +++ sqlprocessor-sbk.xml	1999/12/11 14:24:49	1.2
  @@ -1,3 +1,4 @@
  +<?xml version="1.0" encoding="UTF-8"?>
   <s1 title="SQLProcessor User Guide">
    
   
  
  
  
  1.2       +6 -5      xml-site/sources/cocoon/technologies-sbk.xml
  
  Index: technologies-sbk.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/cocoon/technologies-sbk.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- technologies-sbk.xml	1999/12/03 00:14:03	1.1
  +++ technologies-sbk.xml	1999/12/11 14:24:49	1.2
  @@ -1,3 +1,4 @@
  +<?xml version="1.0" encoding="UTF-8"?>
   <s1 title="Technologies Used">
    
    
  @@ -43,8 +44,8 @@
   
   <p>So, any valid XML document is <ref>well-formed</ref> and an XML document
<ref>valid
   </ref>for one particular DTD may not necessary be valid for another DTD.
  -For example, HTML is not an XML language because the <code>&lt;&lt;br&gt;&gt;</code>
tag
  -is not XML compliant. XHTML (where <code>&lt;&lt;br&gt;&gt;</code>
is replaced by <code>&lt;&lt;br/&gt;&gt;</code>)
  +For example, HTML is not an XML language because the <code>&lt;br&gt;</code>
tag
  +is not XML compliant. XHTML (where <code>&lt;br&gt;</code> is replaced
by <code>&lt;br/&gt;</code>)
   is XML compliant. While HTML pages are not always XML documents (some pages
   might be), XHTML pages are always well-formed and valid if matched against the
   XHTML DTD.</p>
  @@ -76,8 +77,8 @@
     An HTML page is not designed for this. It was designed for <ref>how to present</ref>
     the data.</p>
     <p>When I look at a web page I might see that an author choose to make every
  -  paragraph heading bold with <code>&lt;&lt;font size+1&gt;&gt;</code>.
Yet if I look at
  -  another page I might notice that every paragraph heading was marked up with <code>&lt;&lt;H1&gt;&gt;</code>.
  +  paragraph heading bold with <code>&lt;font size+1&gt;</code>. Yet
if I look at
  +  another page I might notice that every paragraph heading was marked up with <code>&lt;H1&gt;</code>.
     Yet another page may use tables and table headers to format the data. Find me
     every document that has the word <ref>potato</ref> in the paragraph heading
     of the first paragraph.</p>
  @@ -227,7 +228,7 @@
   reason may be used in chain: transformA goes from DTD1 to DTD2 and transformB
   from DTD2 to DTD3 or graphically</p>
   
  -<source>DTD1 ---(transformA)--&gt;&gt; DTD2 ---(transformB)---&gt;&gt;
DTD3</source>
  +<source>DTD1 ---(transformA)--&gt; DTD2 ---(transformB)---&gt; DTD3</source>
   
   <p>We'll call DTD1 the <ref>original DTD</ref> (because its the origin),
DTD2 some <ref>intermediate
   DTD</ref>, DTD3 the <ref>final DTD</ref>. It can be shown that a transformation
can
  
  
  
  1.2       +6 -2      xml-site/sources/cocoon/todo-sbk.xml
  
  Index: todo-sbk.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/cocoon/todo-sbk.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- todo-sbk.xml	1999/12/03 00:14:03	1.1
  +++ todo-sbk.xml	1999/12/11 14:24:49	1.2
  @@ -1,12 +1,16 @@
  +<?xml version="1.0" encoding="UTF-8"?>
   <s1 title="Todo List"><s2 title="showstopper"><li><em>docs</em>
- 
     Finish XML-ize the docs (install, DCP, SQL).
  - </li><li><em>docs</em> - 
  -  Write the HTML/FO stylesheets.
  + </li><li><em>admin</em> - 
  +  Write the user selectable error page.
    </li><li><em>build</em> - 
     Finish Ant build file and clean it up.
    </li><li><em>admin</em> - 
     Make sure all the java.apache.org stuff is removed.
    </li></s2><s2 title="high"><li><em>code</em> - 
  +  Implement "xsl:output" instead of "cocoon-format" PI and redesign
  +  formatting subsystem.
  + </li><li><em>code</em> - 
     Pass request/session parameters to the XSLT processors for dynamic
     stylesheet operation.
    </li><li><em>code</em> - 
  
  
  
  1.2       +4 -3      xml-site/sources/cocoon/WD-xsp-sbk.xml
  
  Index: WD-xsp-sbk.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/sources/cocoon/WD-xsp-sbk.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- WD-xsp-sbk.xml	1999/12/03 00:14:03	1.1
  +++ WD-xsp-sbk.xml	1999/12/11 14:24:49	1.2
  @@ -1,3 +1,4 @@
  +<?xml version="1.0" encoding="UTF-8"?>
   <s1 title="XSP Layer 1">
    
    
  @@ -249,9 +250,9 @@
       &lt;/page&gt;  
     </source>
   
  -  <p>This simple example shows the power of content/logic/style separation. While
the <code>&lt;&lt;title&gt;&gt;</code>
  +  <p>This simple example shows the power of content/logic/style separation. While
the <code>&lt;title&gt;</code>
     tag has a very special meaning in the <ref>page</ref> document type, indicating
the page
  -  title, the <code>&lt;&lt;counter&gt;&gt;</code> element is
needs to be dynamically substituted by
  +  title, the <code>&lt;counter&gt;</code> element is needs to be dynamically
substituted by
     the number of times the document has been requested. The logic that performs such behavior
     is included in tag itself, but unlike other existing server side technologies, the
     behavior is not defined in the page itself, but on the logic sheet that is applied to
  @@ -625,7 +626,7 @@
   <s2 title="Acknowledgements">
     <p>The following people have greatly contributed to the creation and design of
this draft:</p>
     <ul>
  -   <li><p>Ricardo Rocha &lt;&lt;<jump href="mailto:ricardo@apache.org">ricardo@apache.org</jump>&gt;&gt;</p></li>
  +   <li><p>Ricardo Rocha &lt;<jump href="mailto:ricardo@apache.org">ricardo@apache.org</jump>&gt;</p></li>
     </ul>
   </s2>
   
  
  
  

Mime
View raw message