You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xalan.apache.org by dl...@apache.org on 2001/06/25 22:20:16 UTC
cvs commit: xml-xalan/java/xdocs/sources/xalan commandline.xml history.xml readme.xml
dleslie 01/06/25 13:20:16
Modified: java/xdocs/sources/xalan commandline.xml history.xml
readme.xml
Log:
Release notes for 2.2.D4
Revision Changes Path
1.12 +1 -0 xml-xalan/java/xdocs/sources/xalan/commandline.xml
Index: commandline.xml
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/commandline.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- commandline.xml 2001/03/13 21:01:07 1.11
+++ commandline.xml 2001/06/25 20:20:07 1.12
@@ -110,6 +110,7 @@
not well formed XML).</p>
<p>To set stylesheet parameters from the command line, use <br/>
<code>java org.apache.xalan.xslt.Process -PARAM <ref>name value</ref></code></p>
+ <p>The value is passed to the transformer as a String.</p>
<p>Use <code>-URIRESOLVER</code> with a fully qualified class name to utilize a custom implementation of the
<jump href="apidocs/javax/xml/transform/URIResolver.html">URIResolver</jump> TrAX interface to resolve URIs for
xsl:include, xsl:import, and the document() function.</p>
1.8 +48 -0 xml-xalan/java/xdocs/sources/xalan/history.xml
Index: history.xml
===================================================================
RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/history.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- history.xml 2001/06/13 21:53:10 1.7
+++ history.xml 2001/06/25 20:20:09 1.8
@@ -1,4 +1,52 @@
+ <anchor name="dtm"/>
+ <s3 title="Changes for &xslt4j; 2.2.D2">
+ <p>This release includes the following changes:</p>
+ <ul>
+ <li>Deprecation of the <link idref="usagepatterns" anchor="compat">Xalan-Java 1 compatiblity API</link></li>
+ <li>The DTM</li>
+ <li>Other optimization work</li>
+ </ul>
+ <anchor name="dtm"/>
+ <p>The primary focus of the 2.2 Developer releases is incorporation of all our work over the past several months on the Document Table
+ Model (<link idref="dtm">DTM</link>).</p>
+<p>As a result of the changes in *internal* api, you may encounter problems with extensions. We have done some bug fixing in support
+for extensions since 2.2.D1. John Gentilin is working on fixing the SQL library extension,which currently is broken. Please report
+any problems you find (see <link anchor="bugs">bugs</link>).</p>
+
+<p>The DTM and related work provides faster performance and less accumulation of garbage... though it is an
+ongoing battle. Brief summary:</p>
+<ul>
+<li>The DTM identifies nodes with 32-bit integer handles.
+The DTM has many features, including direct character dispatch to SAX2,
+native DTM iterators and "traversers", multiple document management, etc.<br/><br/></li>
+<li>Joe Kesselman's CoRoutine parsers, which are in a threaded SAX flavor
+and in a Xerces parseMore() flavor (no threads). These do away with the
+"race" conditions that occured in the original code, and should make Xalan
+much more robust.<br/><br/></li>
+<li>*Much* more robust XPath itteration. The "waiting" iterators of old are
+no more, and good riddance. There is stil lots more we want to do with
+this mechanism. (There is something here called MatchIterators, but it's
+not being used yet for various reasons. We will be taking advantage of
+these down the line.)<br/><br/></li>
+<li>A fair amount of XObject creation reduction. You can now get boolean,
+number, nodeset, and string values directly from an Expression, instead of
+going through an XObject.<br/><br/></li>
+<li>XMLString, which allows us to work with string objects that don't wrap
+Java's String object. These objects get their character data from an array or
+Fast String Buffer.<br/><br/></li>
+<li>Serializers now only do internal buffering if they know they are writing
+to a FileStream.<br/><br/></li>
+<li>The variable stack mechanism has been redisigned, so that it is no
+longer so interpretive, and we believe it is much more robust.<br/><br/></li>
+<li> Some small amount of stylesheet rewriting (but not yet redundent
+expression elimination), in particular to reduce full RTF creation and
+interpretation.</li>
+</ul>
+<p>&xslt4j; implements two DTM performance features that you can control with the TransformerFactory
+<jump href="apidocs/javax/xml/transform/TransformerFactory.html#setAttribute(java.lang.String, java.lang.Object)">setAttribute()</jump>
+method. See <link idref="dtm" anchor="settings">DTM performance settings</link></p>
+ </s3>
<s3 title="Changes for &xslt4j; 2.1.0">
&xsltcdone;
<p>This release also includes a number of bug fixes to &xslt4j; and TrAX.
1.40 +14 -47 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.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- readme.xml 2001/06/15 16:50:51 1.39
+++ readme.xml 2001/06/25 20:20:10 1.40
@@ -71,60 +71,27 @@
</ul><anchor name="status0"/>
<s2 title="Status">
<ul>
- <li><link anchor="done">Changes since version 2.0.1</link></li>
+ <li><link anchor="done">Changes since version 2.2.D2</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"/><anchor name="dtm"/>
- <s3 title="Changes since &xslt4j; 2.1.0">
- <p>This release includes the following changes:</p>
+ <anchor name="done"/>
+ <s3 title="Changes since &xslt4j; 2.2.D2">
+ <p>This beta release includes the following changes:</p>
<ul>
- <li>Deprecation of the <link idref="usagepatterns" anchor="compat">Xalan-Java 1 compatiblity API</link></li>
- <li>The DTM</li>
- <li>Other optimization work</li>
+ <li>Costin Manolache has slightly modified the CoRoutine stuff so that a you can compile and run everything but the CoRoutineXercesParser without having Xerces on the classpath.<br/><br/></li>
+ <li>Joseph Kesselman added chunked int array stuff to address our scaling problems that Mukund & co. uncovered. This was a fairly mechanical, but still substantial, change. No bugs have yet been discovered that relate to this. This is probably the most controversial change.<br/><br/></li>
+ <li>The Process class now outputs incrementally if the output is standard out. This is mostly for testing purposes, but it makes general sense.<br/><br/></li>
+ <li>Bug was fixed with setting the incremental flag in TransformerFactoryImpl. Clearly the change was made but never tested. Simply a missing 'else'.<br/><br/></li>
+ <li>Fix for Bugzilla Bug 2275, Xalan did not fire the right templates. This was substantial and somewhat risky. Xalan had several problems related to the last() function. Fixes cover four axes files.<br/><br/></li>
+ <li>Change PrintTraceListener to output the file, as well as the line numbers. This is really a feature change, but simple, and aids diagnosing problems with multi-part stylesheets.<br/><br/></li>
+ <li>XPath fix: the XPath API wasn't working correctly due to a problem with with NodeSet/NodeIterator adapters. This fix ended up interacting quite a bit with the #2275 fix.<br/><br/></li>
+ <li>Fix for the Norm Walsh bug posted 06/20/2001: iterators weren't always being cloned correctly from the variable value stack. This fix is not without some risk, though we haven't seen any problems since Scott Boag made it.<br/><br/></li>
+ <li>David Bertoni added missing html element properties to SerializerToHTML.java.<br/><br/></li>
+ <li>Shance Curcuru modified TransformerFactoryImpl.setAttribute() to accept a String ("true" or "false") as well as a Boolean object to set the value of a Boolean attribute.</li>
</ul>
- <anchor name="dtm"/>
- <p>The primary focus of the 2.2 Developer releases is incorporation of all our work over the past several months on the Document Table
- Model (<link idref="dtm">DTM</link>).</p>
-
-<p>As a result of the changes in *internal* api, you may encounter problems with extensions. We have done some bug fixing in support
-for extensions since 2.2.D1. John Gentilin is working on fixing the SQL library extension,which currently is broken. Please report
-any problems you find (see <link anchor="bugs">bugs</link>).</p>
-
-<p>The DTM and related work provides faster performance and less accumulation of garbage... though it is an
-ongoing battle. Brief summary:</p>
-<ul>
-<li>The DTM identifies nodes with 32-bit integer handles.
-The DTM has many features, including direct character dispatch to SAX2,
-native DTM iterators and "traversers", multiple document management, etc.<br/><br/></li>
-<li>Joe Kesselman's CoRoutine parsers, which are in a threaded SAX flavor
-and in a Xerces parseMore() flavor (no threads). These do away with the
-"race" conditions that occured in the original code, and should make Xalan
-much more robust.<br/><br/></li>
-<li>*Much* more robust XPath itteration. The "waiting" iterators of old are
-no more, and good riddance. There is stil lots more we want to do with
-this mechanism. (There is something here called MatchIterators, but it's
-not being used yet for various reasons. We will be taking advantage of
-these down the line.)<br/><br/></li>
-<li>A fair amount of XObject creation reduction. You can now get boolean,
-number, nodeset, and string values directly from an Expression, instead of
-going through an XObject.<br/><br/></li>
-<li>XMLString, which allows us to work with string objects that don't wrap
-Java's String object. These objects get their character data from an array or
-Fast String Buffer.<br/><br/></li>
-<li>Serializers now only do internal buffering if they know they are writing
-to a FileStream.<br/><br/></li>
-<li>The variable stack mechanism has been redisigned, so that it is no
-longer so interpretive, and we believe it is much more robust.<br/><br/></li>
-<li> Some small amount of stylesheet rewriting (but not yet redundent
-expression elimination), in particular to reduce full RTF creation and
-interpretation.</li>
-</ul>
-<p>&xslt4j; implements two DTM performance features that you can control with the TransformerFactory
-<jump href="apidocs/javax/xml/transform/TransformerFactory.html#setAttribute(java.lang.String, java.lang.Object)">setAttribute()</jump>
-method. See <link idref="dtm" anchor="settings">DTM performance settings</link></p>
</s3>
<anchor name="other"/>
<s3 title="Other points of interest">
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-cvs-help@xml.apache.org