xalan-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dles...@apache.org
Subject cvs commit: xml-xalan/java/xdocs/sources/xalan extensionslib.xml readme.xml
Date Thu, 27 Sep 2001 18:57:15 GMT
dleslie     01/09/27 11:57:15

  Modified:    java/xdocs/sources/xalan extensionslib.xml readme.xml
  Log:
  Updates for 2.2.D11
  
  Revision  Changes    Path
  1.19      +10 -13    xml-xalan/java/xdocs/sources/xalan/extensionslib.xml
  
  Index: extensionslib.xml
  ===================================================================
  RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/extensionslib.xml,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  --- extensionslib.xml	2001/08/14 19:09:41	1.18
  +++ extensionslib.xml	2001/09/27 18:57:15	1.19
  @@ -222,26 +222,23 @@
   <li><link anchor="ex-sql">SQL library example</link></li>
   <li><link idref="samples" anchor="sql">SQL library sample applications</link></li>
   </ul>
  -<p><em>**Experimental**</em> Provides extension functions for connecting
to a JDBC data source, executing a query,
  -and optionally working incrementally through a "streamable" result set. <ref>Due
to a bug, caching, not streaming, is currently 
  -the default mode of operation.</ref> </p>
  -<note>Many features of the SQL library, including support for connection pools, parameterized
queries, caching,  
  -and added support for extracting connection information and query parameters from XML source
documents exist
  -thanks to John Gentilin (johnglinux@eyecatching.com), who has also added a number of SQL
library samples.</note>
  -<p><em>The SQL extension use in streaming mode of a single row-set node to
incrementally return a query result set is experimental. If you use streaming mode, you can
only access row elements one at a time moving forward through the result set. The use of XPath
expressions in your stylesheet, for example, that attempt to return nodes from the result
set in any other manner may produce unpredictable results.</em></p>
  -<p><jump href="apidocs/org/apache/xalan/lib/sql/XConnection.html">org.apache.xalan.lib.sql.XConnection</jump>
provides a number 
  -of extension functions that you can use in your stylesheet.</p>
  +<p>Provides extension functions for connecting to a JDBC data source, executing a
query,
  +and working incrementally through a "streamable" result set. Streaming (reuse of a single
row node to traverse the result set) is the default mode of operation. If you want unlimited
access to the entire result set, you can cache the query result set (1 row node for each row
in the result set).</p>
  +<p><em>If you use streaming mode (the default), you can only access row elements
one at a time moving forward through the result set. The use of XPath expressions in your
stylesheet, for example, that attempt to return nodes from the result set in any other manner
may produce unpredictable results.</em></p>
  +<note>Many features of the SQL library, including support for connection pools, parameterized
queries, caching, and added support for extracting connection information and query parameters
from XML source documents exist thanks to John Gentilin (johnglinux@eyecatching.com), who
has also added a number of <link idref="samples" anchor="sql">SQL library samples</link>.</note>
  +<p><jump href="apidocs/org/apache/xalan/lib/sql/XConnection.html">org.apache.xalan.lib.sql.XConnection</jump>
provides a number of extension functions that you can use in your stylesheet.</p>
       <ol>
         <li>new() -- Use one of the XConnection constructors to connect to a data source,
and return an XConnection
          object. You can use one of the constructors creates a connection pool from which
stylesheets can obtain connections 
  -       to a datasource. To support connction pools, SQL library includes a ConnectionPool
interface and a implementation:
  +       to a datasource. To support connection pools, SQL library includes a ConnectionPool
interface and a implementation:
          DefaultConnectionPool. You can also provide your own ConnectionPool implementation.<br/><br/></li>
         <li>query() -- Use the XConnection object query() method to return a "streamable"
result set in the form of a row-set
          node. Work your way through the row-set one row at a time. The same row element
is used over and over again, so you can
          begin "transforming" the row-set before the entire result set has been returned.<br/><br/></li>
          <li>pquery(), addParameter(), addParameterFromElement(), clearParameters()
-- Use the XConnection pquery() method in 
          conjunction with these other methods to set up and execute parameterized queries.<br/><br/></li>
  -       <li>Use disableCacheNodes() to use streaming node, and enableCacheNodes()
to cache the query result set. <br/><br/></li>
  +       <li>Use enableStreamingMode() to use a single row node to "stream" through
the result set, and disableStreamingMode()
  +        to cache the query result set. <br/><br/></li>
         <li>close() -- Use the XConnection object close() method to terminate the connection.</li>
     
       </ol>
       <p>The query() and pquery() extension functions return a Document node that contains
(as needed) an array of column-header elements, 
  @@ -338,11 +335,11 @@
           &lt;xsl:variable name="table" select='sql:query($products, $query)'/&gt;
             &lt;TR&gt;
             &lt;!-- Get column-label attribute from each column-header--&gt;
  -          &lt;xsl:for-each select="$table/row-set/column-header"&gt;
  +          &lt;xsl:for-each select="$table/sql/metadata/column-header"&gt;
               &lt;TH&gt;&lt;xsl:value-of select="@column-label"/&gt;&lt;/TH&gt;
             &lt;/xsl:for-each&gt;
             &lt;/TR&gt;
  -          &lt;xsl:apply-templates select="$table/row-set/row"/&gt;
  +          &lt;xsl:apply-templates select="$table/sql/row-set/row"/&gt;
             &lt;xsl:text&gt;&amp;#10;&lt;/xsl:text&gt;
           &lt;/TABLE&gt;
         &lt;/BODY&gt;
  
  
  
  1.51      +5 -4      xml-xalan/java/xdocs/sources/xalan/readme.xml
  
  Index: readme.xml
  ===================================================================
  RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/readme.xml,v
  retrieving revision 1.50
  retrieving revision 1.51
  diff -u -r1.50 -r1.51
  --- readme.xml	2001/08/29 15:12:26	1.50
  +++ readme.xml	2001/09/27 18:57:15	1.51
  @@ -71,16 +71,17 @@
    </ul><anchor name="status0"/>
     <s2 title="Status">
      <ul>
  -    <li><link anchor="done">Changes since version 2.2.D9</link></li>
  +    <li><link anchor="done">Changes since version 2.2.D10</link></li>
       <li><link anchor="other">Other points of interest</link></li>
       <li><link anchor="bugs">Bugs</link></li>
       <li><link anchor="status">Version of Xerces to use</link></li>
       <li><link anchor="to-do">To-do tasks for future &xslt4j; releases</link></li>
      </ul>
        <anchor name="done"/>
  -     <s3 title="Changes since &xslt4j; 2.2.D9">
  -     <p>&xslt4j-current; is a Developer release. For enhanced performance, it
incorporates the 
  -     <link idref="dtm">DTM</link>.</p>
  +     <s3 title="Changes since &xslt4j; 2.2.D10">
  +     <p>&xslt4j-current; is a Developer release. For enhanced performance, the
current series of Developer releases incorporate
  +     the <link idref="dtm">DTM</link>. We believe Xalan with the DTM has reached
a level of stability that warrants a
  +     standard "User" release. Accordingly, we plan to release &xslt4j; 2.2 soon.</p>
        <note>The SQL Extension library has been updated to work with DTM.</note>
        &done-j;
        </s3>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-cvs-help@xml.apache.org


Mime
View raw message