Return-Path: Delivered-To: apmail-xml-xalan-cvs-archive@xml.apache.org Received: (qmail 11711 invoked by uid 500); 27 Sep 2001 18:58:13 -0000 Mailing-List: contact xalan-cvs-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: Delivered-To: mailing list xalan-cvs@xml.apache.org Received: (qmail 11677 invoked from network); 27 Sep 2001 18:58:13 -0000 Date: 27 Sep 2001 18:57:15 -0000 Message-ID: <20010927185715.92400.qmail@icarus.apache.org> From: dleslie@apache.org To: xml-xalan-cvs@apache.org Subject: cvs commit: xml-xalan/java/xdocs/sources/xalan extensionslib.xml readme.xml X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 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 @@
  • SQL library example
  • SQL library sample applications
  • -

    **Experimental** Provides extension functions for connecting to a JDBC data source, executing a query, -and optionally working incrementally through a "streamable" result set. Due to a bug, caching, not streaming, is currently -the default mode of operation.

    -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. -

    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.

    -

    org.apache.xalan.lib.sql.XConnection provides a number -of extension functions that you can use in your stylesheet.

    +

    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).

    +

    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.

    +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. +

    org.apache.xalan.lib.sql.XConnection provides a number of extension functions that you can use in your stylesheet.

    1. 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.

    2. 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.

    3. pquery(), addParameter(), addParameterFromElement(), clearParameters() -- Use the XConnection pquery() method in conjunction with these other methods to set up and execute parameterized queries.

    4. -
    5. Use disableCacheNodes() to use streaming node, and enableCacheNodes() to cache the query result set.

    6. +
    7. Use enableStreamingMode() to use a single row node to "stream" through the result set, and disableStreamingMode() + to cache the query result set.

    8. close() -- Use the XConnection object close() method to terminate the connection.

    The query() and pquery() extension functions return a Document node that contains (as needed) an array of column-header elements, @@ -338,11 +335,11 @@ <xsl:variable name="table" select='sql:query($products, $query)'/> <TR> <!-- Get column-label attribute from each column-header--> - <xsl:for-each select="$table/row-set/column-header"> + <xsl:for-each select="$table/sql/metadata/column-header"> <TH><xsl:value-of select="@column-label"/></TH> </xsl:for-each> </TR> - <xsl:apply-templates select="$table/row-set/row"/> + <xsl:apply-templates select="$table/sql/row-set/row"/> <xsl:text>&#10;</xsl:text> </TABLE> </BODY> 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 @@

      -
    • Changes since version 2.2.D9
    • +
    • Changes since version 2.2.D10
    • Other points of interest
    • Bugs
    • Version of Xerces to use
    • To-do tasks for future &xslt4j; releases
    - -

    &xslt4j-current; is a Developer release. For enhanced performance, it incorporates the - DTM.

    + +

    &xslt4j-current; is a Developer release. For enhanced performance, the current series of Developer releases incorporate + the DTM. 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.

    The SQL Extension library has been updated to work with DTM. &done-j;
    --------------------------------------------------------------------- To unsubscribe, e-mail: xalan-cvs-unsubscribe@xml.apache.org For additional commands, e-mail: xalan-cvs-help@xml.apache.org