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...@locus.apache.org on 2000/11/10 18:48:10 UTC
cvs commit: xml-xalan/xdocs/sources/xalan DONE STATUS history.xml index.xml
dleslie 00/11/10 09:48:08
Modified: xdocs/sources/xalan DONE STATUS history.xml index.xml
Log:
Updates fo Xalan-J 1.2.1
Revision Changes Path
1.27 +7 -17 xml-xalan/xdocs/sources/xalan/DONE
Index: DONE
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/DONE,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- DONE 2000/10/13 15:27:13 1.26
+++ DONE 2000/11/10 17:48:07 1.27
@@ -1,22 +1,12 @@
-<s3 title="Changes since &xslt4j; version 1.2.D02">
+<s3 title="Changes since &xslt4j; version 1.2.">
<p>We have applied a number of enhancements and bug fixes, including patches submitted by developers to <human-resource-ref idref="xalandev"/>. If you run across a problem with &xslt4j;, we strongly encourage you to write a patch and submit it to us. We will review it to make sure it doesn't break something else, and (assuming it doesn't) include it in our next release. In the interest of fixing bugs, adding enhancements, and addressing a host of thorny design issues, we sincerely want (and need!) your active participation in the ongoing development of Xalan.</p>
<ul>
- <li>&xslt4j; now suports UTF-16 output encoding.<br/><br/></li>
- <li>We incorporated an updated BSF (support for extension elements and functions) that supports Mozilla Rhino js.jar 1.5. The new bsf.jar replaces the older bsf.jar and bsfengines.jar. <em>If you are using Javascript extensions, you must now use js.jar 1.5. Mozilla Rhino 1.4 R3 is no longer supported.</em><br/><br/></li>
- <li>Costin Manolache submitted a patch that isolates all BSF-dependent code in org.apache.xalan.xpath.XSLTJavaClassEngine.<br/><br/></li>
-<li>We have added a custom processing instruction that you can use to instruct the &xslt4j; processor not to cache an XML document.<br/><br/>
-To use this processing instruction, declare the following namespace in the stylesheet element:<br/>
- <code>xmlns:xalan="http://xml.apache.org/xslt"</code><br/>
-and include the following processing instruction in an xsl:for-each loop or xsl:templates-apply where you are using the document() function to read external documents:<br/>
- <code><?xalan:doc-cache-off?></code><br/><br/></li>
- <li>Costin Manolache submitted a new parser liaison class (org.apache.xalan.xpath.xml.JaxpLiaison) and patches to a number of existing classes so that you should be able to use &xslt4j; with any XML parser that implements <resource-ref idref="jaxp"/>.<br/><br/></li>
- <li>We modified SimpleNodeLocator to fix a problem matching [predicate]/node patterns.<br/><br/></li>
- <li>We modified ElemNumber.java to make accessing the Xalan resource bundle thread safe.<br/><br/></li>
- <li>We have improved the performance of keys by no longer allowing <xsl:key> elements to use key() functions in the match or use attribute.<br/><br/></li>
- <li>Gary Peskin submitted a patch that fixes step pattern root matches.<br/><br/></li>
- <li>We fixed org.apache.xalan.xslt.TemplateList to match wildcard patterns.<br/><br/></li>
- <li>Xalan now correctly observes import precedence when it evaluates a variable declared and set in more than one
- stylesheet.<br/><br/></li>
+<li>Gary Peskin posted fixes to the node-set extension function.<br/><br/></li>
+<li>Benoit Cerrina submitted a Tokezenizer extension function.<br/><br/></li>
+<li>We fixed a bug in which a global variable was declared to be out of scope when referenced by another variable.<br/><br/></li>
+<li>We also fixed a bug evaluating global variables in SAX processing.<br/><br/></li>
+<li>We fixed a bug in which the default XSLT processor was failing to shift to a Xerces DOM parser to process DOM input.<br/><br/></li>
+<li>Ritesh Kumar submitted a fix to the sample servlet to correctly obtain the server port from the HttpServletRequest object.<br/><br/></li>
</ul>
</s3>
1.18 +1 -1 xml-xalan/xdocs/sources/xalan/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/STATUS,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- STATUS 2000/10/13 14:55:55 1.17
+++ STATUS 2000/11/10 17:48:07 1.18
@@ -15,7 +15,7 @@
<li>Begin the adoption of the TRaX (Transformations for XML) interfaces</li>
<li>Take advantage of the <jump href="http://www.megginson.com/SAX/Java/index.html">SAX 2</jump> and <jump href="http://www.w3.org/TR/DOM-Level-2/">DOM level 2</jump> packages</li>
</ol>
- <p>For an overview of the 2.0 design, see <jump href="http://xml.apache.org/xalan/design/design1_1_0.html">Xalan-J 2.0 Design</jump>. The source tree (still pre-alpha) is in the <jump href="http://xml.apache.org/websrc/cvsweb.cgi/xml-xalan/java/src/">Apache CVS Repository: xml-xalan/java/src</jump>. Pre-alpha Xalan-J 2.0 <jump href="http://xml.apache.org/xalan-j/apidocs/index.html">Javadoc</jump> is also periodically updated on the xml.apache.org Website.</p>
+ <p>For the alpha release of Xalan-J 2, see <jump href="http://xml.apache.org/xalan-j/index.html">Xalan-J 2.0 Alpha release</jump>.</p>
<p>As part of the xml.apache team, members of the &xslt4j; team are also exploring options to upgrade the integration of all
the xml.apache projects, including Xalan, Xerces, Cocoon, and FOP.</p>
<p>The more individuals who join in the design, development, testing, documentation, and use of
1.4 +23 -0 xml-xalan/xdocs/sources/xalan/history.xml
Index: history.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/history.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- history.xml 2000/10/13 14:55:57 1.3
+++ history.xml 2000/11/10 17:48:07 1.4
@@ -1,3 +1,26 @@
+<s3 title="Changes for &xslt4j; version 1.2.">
+<p>We have applied a number of enhancements and bug fixes, including patches submitted by developers to <human-resource-ref idref="xalandev"/>. If you run across a problem with &xslt4j;, we strongly encourage you to write a patch and submit it to us. We will review it to make sure it doesn't break something else, and (assuming it doesn't) include it in our next release. In the interest of fixing bugs, adding enhancements, and addressing a host of thorny design issues, we sincerely want (and need!) your active participation in the ongoing development of Xalan.</p>
+<ul>
+ <li>&xslt4j; now suports UTF-16 output encoding.<br/><br/></li>
+ <li>We incorporated an updated BSF (support for extension elements and functions) that supports Mozilla Rhino js.jar 1.5. The new bsf.jar replaces the older bsf.jar and bsfengines.jar. <em>If you are using Javascript extensions, you must now use js.jar 1.5. Mozilla Rhino 1.4 R3 is no longer supported.</em><br/><br/></li>
+ <li>Costin Manolache submitted a patch that isolates all BSF-dependent code in org.apache.xalan.xpath.XSLTJavaClassEngine.<br/><br/></li>
+<li>We have added a custom processing instruction that you can use to instruct the &xslt4j; processor not to cache an XML document.<br/><br/>
+To use this processing instruction, declare the following namespace in the stylesheet element:<br/>
+ <code>xmlns:xalan="http://xml.apache.org/xslt"</code><br/>
+and include the following processing instruction in an xsl:for-each loop or xsl:templates-apply where you are using the document() function to read external documents:<br/>
+ <code><?xalan:doc-cache-off?></code><br/><br/></li>
+ <li>Costin Manolache submitted a new parser liaison class (org.apache.xalan.xpath.xml.JaxpLiaison) and patches to a number of existing classes so that you should be able to use &xslt4j; with any XML parser that implements <resource-ref idref="jaxp"/>.<br/><br/></li>
+ <li>We modified SimpleNodeLocator to fix a problem matching [predicate]/node patterns.<br/><br/></li>
+ <li>We modified ElemNumber.java to make accessing the Xalan resource bundle thread safe.<br/><br/></li>
+ <li>We have improved the performance of keys by no longer allowing <xsl:key> elements to use key() functions in the match or use attribute.<br/><br/></li>
+ <li>Gary Peskin submitted a patch that fixes step pattern root matches.<br/><br/></li>
+ <li>We fixed org.apache.xalan.xslt.TemplateList to match wildcard patterns.<br/><br/></li>
+ <li>Xalan now correctly observes import precedence when it evaluates a variable declared and set in more than one
+ stylesheet.<br/><br/></li>
+</ul>
+
+</s3>
+
<s3 title="Changes for &xslt4j; version 1.2.D02">
<p>We applied the following bug fixes</p>
<ul>
1.11 +1 -1 xml-xalan/xdocs/sources/xalan/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/index.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- index.xml 2000/10/13 14:55:58 1.10
+++ index.xml 2000/11/10 17:48:07 1.11
@@ -64,7 +64,7 @@
is a complete and robust implementation of the W3C Recommendations for XSL Transformations (XSLT) and the XML Path Language
(XPath).</p>
<p>Xalan can be used from the command line, in an applet or a servlet, or as a module in other program. By default, it uses the Xerces XML parser, but it can interface to any XML parser that conforms to the DOM level 2 or SAX level 1 specification.</p>
- <p>This release incorporates a number of performance enhancements and bug fixes, including patches submitted to the <human-resource-ref idref="xalandev"/>. For example, we have added support for UTF-16 output encoding, and we updated support for Javascript extensions to work with Mozilla Rhino js.jar version 1.5 (1.4 R3 is no longer supported). For the details, see <link idref="readme">Release Notes</link>.</p>
+ <p>This release incorporates a number of performance enhancements and bug fixes, including patches submitted to the <human-resource-ref idref="xalandev"/>. For example, we have added support for new extension functions and we have fixed a couple of bugs pertaining to the evaluation of vairables. For the details, see <link idref="readme">Release Notes</link>.</p>
</s2>
<s2 title="How do I get it?">