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 dynamic.xml installing.xml ldapprocessor.xml sqlprocessor.xml
Date Thu, 13 Apr 2000 10:43:51 GMT
stefano     00/04/13 03:43:51

  Modified:    xdocs    dynamic.xml installing.xml ldapprocessor.xml
                        sqlprocessor.xml
  Log:
  fixed the old PI format + installation doc cleanups
  
  Revision  Changes    Path
  1.2       +1 -1      xml-cocoon/xdocs/dynamic.xml
  
  Index: dynamic.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/xdocs/dynamic.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- dynamic.xml	2000/01/27 03:46:03	1.1
  +++ dynamic.xml	2000/04/13 10:43:50	1.2
  @@ -122,7 +122,7 @@
   {
             
     String dummy = "<?xml version=\"1.0\"?>" 
  -      + "<?cocoon:format type=\"text/html\"?>"
  +      + "<?cocoon-format type=\"text/html\"?>"
         + "<html><body>"
         + "<h1 align=\"center\">"
             + "Hello from a dummy page"
  
  
  
  1.10      +25 -7     xml-cocoon/xdocs/installing.xml
  
  Index: installing.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/xdocs/installing.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- installing.xml	2000/03/30 00:33:36	1.9
  +++ installing.xml	2000/04/13 10:43:50	1.10
  @@ -53,8 +53,13 @@
     </p>
   
     <p>
  -   In the <code>/lib</code> directory you'll find all the required packages.
  -   Now jump to the installation instructions for your servlet engine.
  +   In the <code>/bin</code> directory you'll find the <code>cocoon.jar</code>
  +   jar package that contains the Cocoon binary files, while the  <code>/lib</code>

  +   directory contains all the libraries required for complete Cocoon operation.
  +   While these packages may not be the most up-to-date versions, they are
  +   guaranteed and tested to work properly with Cocoon so, we suggest that you
  +   use them. Note, however, that they were all redistributed untouched from
  +   their original distributions.
     </p>
   
     <note>
  @@ -89,15 +94,15 @@
   
   <source>
   wrapper.classpath=/usr/local/java/jdk/lib/tools.jar
  -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/cocoon/bin/cocoon.jar
  +wrapper.classpath=/usr/local/java/cocoon/lib/xerces.jar
  +wrapper.classpath=/usr/local/java/cocoon/lib/xalan.jar
  +wrapper.classpath=/usr/local/java/cocoon/lib/fop.jar
   ...
   </source>
   
      <note>
  -    The <code>cocoon.jar</code> package <strong>must</strong> be
added to the 
  +    The <code>./bin/cocoon.jar</code> package <strong>must</strong>
be added to the 
       servlet engine classpath in order for the XSP subsystem to work correctly.
       We perfectly understand this as a limitation to Cocoon flexibility, and 
       we are working hard to make it possible for multiple cocoon instances to
  @@ -148,6 +153,13 @@
       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>
  +    You need to make sure that you have the following line uncommented in your
  +    <code>httpd.conf</code> or Apache will not be able to start:
  +   </p>
  +   
  +<source>LoadModule action_module /path/to/mod_actions.so</source>
   
      <p>
       Restart both Apache and Apache JServ and try accessing the Cocoon status page:
  @@ -471,6 +483,12 @@
      <td>Apache 1.3.12</td>
      <td>Apache JServ 1.1</td>
      <td>Sun JDK 1.2.1 (SGI)</td>
  +  </tr>
  +  <tr>
  +   <td>Microsoft Windows 2000 Professional</td>
  +   <td>Apache 1.3.12</td>
  +   <td>Apache JServ 1.1</td>
  +   <td>Sun JDK 1.2.2</td>
     </tr>
     </table>
   
  
  
  
  1.2       +7 -8      xml-cocoon/xdocs/ldapprocessor.xml
  
  Index: ldapprocessor.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/xdocs/ldapprocessor.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- ldapprocessor.xml	2000/01/27 03:46:03	1.1
  +++ ldapprocessor.xml	2000/04/13 10:43:50	1.2
  @@ -19,18 +19,17 @@
   		</s1>
   		<s1 title="Configuration">
   			<p>Add this PI to the XML files to which you wish to add LDAP queries:</p>
  -			<source>&lt;?cocoon:process type="ldap"?&gt;</source>
  +			<source>&lt;?cocoon-process type="ldap"?&gt;</source>
   			<p>You probably want this before any "xslt" processing directives. Then add LDAP
connection information to your XML files. The tagset for LDAP server defitions looks like
this:</p>
  -			<source>&lt;ldap-defs&gt;
  +<source>&lt;ldap-defs&gt;
    &lt;ldap-server name=foo_server"&gt;
     &lt;initializer&gt;com.sun.jndi.ldap.LdapCtxFactory&lt;/initializer&gt;
     &lt;ldap-serverurl&gt;ldap://ldap.weber.edu&lt;/ldap-serverurl&gt;
    &lt;/ldap-server&gt;
  -&lt;/ldap-defs&gt;
  -</source>
  +&lt;/ldap-defs&gt;</source>
   			<p>This tagset will be removed from the document after processing.</p>
   			<p>In addition to the ldap-server element, you can also have querydefs tags in
your ldap-defs node. A ldap-defs node must have a unique name attribute. ldap-query tags (described
below) may reference a querydefs tag in their defs attribute, which causes the ldap-query
tag's attributes to default to the attributes of the querydefs tag. This is useful for setting
commonly used groups of attributes. You may also specify a default querydefs. Here is an example:</p>
  -			<source>&lt;querydefs name="standard" doc-element="options" 
  +<source>&lt;querydefs name="standard" doc-element="options" 
     row-element="option" server="foo"/&gt;
   &lt;query defs="standard"/&gt;</source>
   			<p>is equivalent to</p>
  @@ -39,11 +38,11 @@
   		</s1>
   		<s1 title="Usage">
   			<p>Add LDAP queries to your XML files. The tagset looks like this:</p>
  -			<source>&lt;ldap-query server="foo_server"&gt;
  +<source>&lt;ldap-query server="foo_server"&gt;
    sn=*Green*
   &lt;/ldap-query&gt;</source>
   			<p>This will be replaced by a tagset that looks something like this:</p>
  -			<source>&lt;ldapsearch&gt;
  +<source>&lt;ldapsearch&gt;
    &lt;searchresult ID="CN=DGREEN,OU=TBE,OU=AST,OU=ACAD,O=WSU"&gt;
     &lt;telephonenumber&gt;801-626-6821&lt;/telephonenumber&gt;
     &lt;facsimiletelephonenumber&gt;801-626-6650&lt;/facsimiletelephonenumber&gt;
  @@ -62,7 +61,7 @@
    &lt;/searchresult&gt;
   &lt;/ldapsearch&gt;</source>
   			<p>You can also have the LdapProcessor substitute values from the servlet request
into your query. The syntax for that is:</p>
  -			<source>&lt;ldap-query name="foo_server"&gt;
  +<source>&lt;ldap-query name="foo_server"&gt;
    sn=*{@name}*
   &lt;/ldap-query&gt;</source>
   			<p>This is, of course, highly configurable by setting attributes of the query
tag. A partial list of attributes is:</p>
  
  
  
  1.2       +2 -2      xml-cocoon/xdocs/sqlprocessor.xml
  
  Index: sqlprocessor.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/xdocs/sqlprocessor.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- sqlprocessor.xml	2000/01/27 03:46:03	1.1
  +++ sqlprocessor.xml	2000/04/13 10:43:50	1.2
  @@ -15,9 +15,9 @@
   
   	<s1 title="Configuration">
   		<p>Add this PI to the XML files to which you wish to add SQL queries:</p>
  -		<source>&lt;?cocoon:process type="sql"?&gt;</source>
  +		<source>&lt;?cocoon-process type="sql"?&gt;</source>
   		<p>You probably want this before any "xslt" processing directives. Then add SQL
connection information to your XML files. The tagset for connection defitions looks like this:</p>
  -		<source>&lt;connectiondefs&gt;
  +<source>&lt;connectiondefs&gt;
    &lt;connection name="foo_connection"&gt;
     &lt;driver&gt;org.gjt.mm.mysql.Driver&lt;/driver&gt;
     &lt;dburl&gt;jdbc:mysql://mysql.example.com/foo_database&lt;/dburl&gt;
  
  
  

Mime
View raw message