nicolaken    02/03/19 06:21:29

  Modified:    .        changes.xml
               src/documentation/xdocs/ctwig ctwig-basic03.xml
               src/documentation/xdocs/developing deli.xml httprequest.xml
               src/documentation/xdocs/installing index.xml
  Log:
  Changed references in the documentation of cocoon.xconf to WEB-INF/cocoon.xconf .
  Reflected latest commits in changes.xml.
  
  Revision  Changes    Path
  1.124     +26 -1     xml-cocoon2/changes.xml
  
  Index: changes.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/changes.xml,v
  retrieving revision 1.123
  retrieving revision 1.124
  diff -u -r1.123 -r1.124
  --- changes.xml       19 Mar 2002 09:06:12 -0000      1.123
  +++ changes.xml       19 Mar 2002 14:21:29 -0000      1.124
  @@ -4,7 +4,7 @@
   
   <!--
     History of Cocoon changes
  -  $Id: changes.xml,v 1.123 2002/03/19 09:06:12 sylvain Exp $
  +  $Id: changes.xml,v 1.124 2002/03/19 14:21:29 nicolaken Exp $
   -->
   
   <changes title="History of Changes">
  @@ -34,6 +34,24 @@
    </devs>
   
    <release version="@version@" date="@date@">
  +  <action dev="NKB" type="add">
  +    Added new "gump" target to the build, to be used as a general
  +    test of Cocoon code. To be used by Gump.
  +    It calls docs, javadocs, test and package.  
  +    Gump descriptor has been modified to use it;
  +    now we also have automatic javadoc creation.
  +  </action>
  +  <action dev="NKB" type="update">
  +    cocoon.xconf is moved in WEB-INF for security reasons. 
  +    The documentation has been updated to reflect the change.
  +  </action>
  +  <action dev="NKB" type="update">
  +   Partial commit of new samples structure.
  +   Samples go in samples/ dir with theit own sitemap.
  +   All scratchpad samples that are in the samples/ subdir are 
  +   copied in webapp samples automatically by installscratchpadwar 
  +   target.  
  +  </action>
     <action dev="SW" type="update">
      New "set-content-length" configuration for FOPSerializer to allow
      streaming of large PDFs (default is true for backwards compatibility).
  @@ -47,6 +65,13 @@
      the docs are generated with the TreeProcessor,
      the docs generation uses JispStore.
     </action>
  +  <action dev="NKB" type="add">
  +    Added new targets:
  +    "installwar"  asks for the directory in which to put
  +    the war and makes it.
  +    "installscratchpadwar"  does the same but incudes
  +    scratchpad libs ans samples.
  +  </action>  
     <action dev="NKB" type="add">
      New POI HSSF Serializer; outputs to the .xls (not .xsl) file format.
      Added samples as legacy file format support.
  
  
  
  1.2       +1 -1      xml-cocoon2/src/documentation/xdocs/ctwig/ctwig-basic03.xml
  
  Index: ctwig-basic03.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/src/documentation/xdocs/ctwig/ctwig-basic03.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- ctwig-basic03.xml 3 Jan 2002 12:31:02 -0000       1.1
  +++ ctwig-basic03.xml 19 Mar 2002 14:21:29 -0000      1.2
  @@ -65,7 +65,7 @@
   </xsl:stylesheet>]]></source>
                                <p>You will note that the logicsheet has a reference 
to the ctwig namespace.  This <strong>must</strong> match the namespace used in the 
XSP page.  The logicsheet uses a standard XSL template match to find the reference to 
"ctwig:greeting" and replace it with the logic.</p>
                                <p><em>Again, please note that this example uses 
"http://apache.org/xsp"; as the XSP namespace.  This is different to older C1 based 
examples and should be used instead.  If you do not then any logicsheet example 
definitely will not work.</em></p>
  -                             <p>To make this work firstly make sure that 
basic3-01.xml in the {TOMCAT_HOME}\webapps\cocoon\ctwig\xsp folder.  This will allow 
it to be captured by the same sitemap command that is used in the previous examples.  
Secondly, make sure that the ctwig logicsheet (ctwig.xsl) is in 
{TOMCAT_HOME}/webapps/cocoon/WEB-INF/classes/com/pigbite/logicsheets folder.  The 
final thing to do is to add a reference to the logicsheet source in to C2 so it knows 
where to go and find it.  This is done by adding the following construct to 
{TOMCAT_HOME}\webapps\cocoon\cocoon.xconf:</p>
  +                             <p>To make this work firstly make sure that 
basic3-01.xml in the {TOMCAT_HOME}\webapps\cocoon\ctwig\xsp folder.  This will allow 
it to be captured by the same sitemap command that is used in the previous examples.  
Secondly, make sure that the ctwig logicsheet (ctwig.xsl) is in 
{TOMCAT_HOME}/webapps/cocoon/WEB-INF/classes/com/pigbite/logicsheets folder.  The 
final thing to do is to add a reference to the logicsheet source in to C2 so it knows 
where to go and find it.  This is done by adding the following construct to 
{TOMCAT_HOME}\webapps\cocoon\WEB-INF\cocoon.xconf:</p>
                                <source><![CDATA[
     <builtin-logicsheet>
       <parameter name="prefix" value="ctwig"/>
  
  
  
  1.8       +1 -1      xml-cocoon2/src/documentation/xdocs/developing/deli.xml
  
  Index: deli.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/src/documentation/xdocs/developing/deli.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- deli.xml  23 Feb 2002 23:26:22 -0000      1.7
  +++ deli.xml  19 Mar 2002 14:21:29 -0000      1.8
  @@ -199,7 +199,7 @@
                                <p>In order to use DELI you need to configure Deli and 
specify
   the configuration file. You can either
   do this in <code>deli.xconf</code> in which case you will need to rebuild
  -Cocoon or change the deployed <code>cocoon.xconf</code> in the web-server 
directory:</p>
  +Cocoon or change the deployed <code>cocoon.xconf</code> in the web-server WEB-INF 
directory:</p>
                                <source><![CDATA[
     <deli class="org.apache.cocoon.components.deli.DeliImpl">
       <parameter name="deli-config-file" 
value="resources/deli/config/deliConfig.xml"/>
  
  
  
  1.2       +1 -1      xml-cocoon2/src/documentation/xdocs/developing/httprequest.xml
  
  Index: httprequest.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/src/documentation/xdocs/developing/httprequest.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- httprequest.xml   3 Jan 2002 12:31:03 -0000       1.1
  +++ httprequest.xml   19 Mar 2002 14:21:29 -0000      1.2
  @@ -99,7 +99,7 @@
                         <link href="avalon.html">Avalon</link> Components.</p>
                  <p>For our study, we need the standard <code>cocoon.xconf</code> file
                         of Cocoon @version@.</p>
  -               <p>It can be found in <code>${cocoon}/cocoon.xconf</code>.</p> 
  +               <p>It can be found in 
<code>${cocoon}/WEB-INF/cocoon.xconf</code>.</p> 
                  <source><![CDATA[
   <?xml version="1.0"?>
   
  
  
  
  1.15      +1 -1      xml-cocoon2/src/documentation/xdocs/installing/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/src/documentation/xdocs/installing/index.xml,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- index.xml 17 Mar 2002 22:25:12 -0000      1.14
  +++ index.xml 19 Mar 2002 14:21:29 -0000      1.15
  @@ -879,7 +879,7 @@
           <li>
             Build the Cocoon webapp as described above.
           </li>
  -        <li>Modify <code>cocoon/build/cocoon/webapp/cocoon.xconf</code>.
  +        <li>Modify <code>cocoon/build/cocoon/webapp/WEB-INF/cocoon.xconf</code>.
             Replace xslt-processor definition using TRAX XSLT transformer factory by
             xslt-processor definition using Xalan transformer factory explicitly.
             Your xslt-processor definition should look like the code snippet below.
  
  
  

----------------------------------------------------------------------
In case of troubles, e-mail:     [EMAIL PROTECTED]
To unsubscribe, e-mail:          [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to