dleslie 01/06/12 12:41:43
Modified: java/xdocs/sources/xalan extensionslib.xml readme.xml
Log:
minor edits for Xalan-J 2.2.D1
Revision Changes Path
1.14 +1 -0 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.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- extensionslib.xml 2001/05/16 18:30:04 1.13
+++ extensionslib.xml 2001/06/12 19:41:42 1.14
@@ -213,6 +213,7 @@
<code>hasSameNodes(node-set1, node-set2)</code> returns true if both node-set1 and
node-set2 contain exactly the same set of nodes.</p>
</s2><anchor name="sql"/>
<s2 title= "SQL library">
+<p><em>[broken in &xslt4j-current; -- does not work with DTM]</em></p>
<ul>
<li><link anchor="sqlconn">Setting up a connection</link></li>
<li><link anchor="sqlparam">Parameterized queries</link></li>
1.36 +6 -7 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.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- readme.xml 2001/06/12 18:27:59 1.35
+++ readme.xml 2001/06/12 19:41:43 1.36
@@ -80,7 +80,7 @@
<anchor name="done"/>
<s3 title="Changes since &xslt4j; 2.2.D1">
<p>We have moved the DTM_EXP branch to the main branch, incorporating all our work
on the <link idref="whatsnew" anchor="dtm">DTM</link> into the Xalan source tree.
-The branch is not absolutely perfect, but it's pretty damn good, and we think
+The branch is not absolutely perfect, but it's in pretty good shape, and we think
any final polishing should be done on the main branch. We would also like
to get any ongoing bug fixes into the DTM version instead of the existing
trunk.</p>
@@ -88,14 +88,13 @@
<p>We expect that developers initially might encounter some issues
with extensions (a fair amount of *internal* api has changed), but we don't
think we can discover these and resolve them one way or the other until we
-get it in the mainstream.</p>
+get th DTM into the mainstream.</p>
<p>We will branch the existing trunk, so that people can still work off that if
they absolutely have to.</p>
-<p>We won't immediately merge any of the bug fixes from the last two weeks
-(since we last did a merge to DTM_EXP). Instead over the next couple of
-days we will merge any bugfixes in, or the bugfix authors can do it.</p>
+<p>We will not immediately merge any of the bug fixes since we last did a merge to
DTM_EXP. We will merge bugfixes in soon,
+or the bugfix authors can do so.</p>
<p>The SQL extension will be broken to start out with. John Gentilin is
working on this, and we hope it will be functional within a week or two.</p>
@@ -134,11 +133,11 @@
<p>With the setAttribute feature of the TransformerFactory, the calling application
can control overall behavior of the Xalan engine. The following are feature URLs
implemented by Xalan.</p>
<p><code>FEATURE_INCREMENTAL =
"http://xml.apache.org/xalan/features/incremental";;</code></p>
-<p>This feature allows a user to specify whether or not to try to do an incremental
transform. If the feature is set to true and we are using SAX, we will run the
transform in one thread and the parse in another. If the feature is set to false,
which is the default value, both the transform and the parse will be done on the same
thread. If Xerces is the parser being used, we will do an incremental transform on a
single thread using the "parse on demand" Xerces feature if this feature is set to
true. </p>
+<p>This feature allows a user to specify whether or not to try to do an incremental
transform. If the feature is set to true and we are using SAX, we will run the
transform in one thread and the parse in another. If the feature is set to false,
which is the default, both the transform and the parse are perofrmed on the same
thread. If the parser is Xerces and this feature is set to true, we will do an
incremental transform on a single thread using the "parse on demand" Xerces
feature.</p>
<p><code>FEATURE_OPTIMIZE =
"http://xml.apache.org/xalan/features/optimize";;</code></p>
-<p>This feature allows a tool that uses Xalan to turn off optimizations that may
involve structural rewrites of the stylesheet. If the tool is relying on the
structure of the elements being the same as the stylesheet, it should set this value
to false. The default for this value is true.</p>
+<p>This feature allows a tool that uses Xalan to turn off optimizations that may
involve structural rewrites of the stylesheet. If the tool is relying on the
structure of the elements being the same as the stylesheet, it should set this value
to false. The default setting is true.</p>
</s3>
<anchor name="other"/>
<s3 title="Other points of interest">
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
