dleslie 00/10/13 07:56:24
Modified: xdocs/sources/xalan BUGS DONE STATUS commandline.xml
history.xml index.xml readme.xml resources.xml
Log:
Final (I hope) doc updates for xalan-j 2.
Revision Changes Path
1.12 +1 -7 xml-xalan/xdocs/sources/xalan/BUGS
Index: BUGS
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/BUGS,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- BUGS 2000/08/22 20:28:19 1.11
+++ BUGS 2000/10/13 14:55:52 1.12
@@ -4,15 +4,12 @@
<li>When format-number() should format NaN or infinity, it generates the
wrong string if default strings are used. Workaround: declare the strings in an
xsl:decimal-format instruction at the top of the stylesheet.<br/><br/></li>
<li>A "not serializable exception" occurs when you attempt to run a
precompiled stylesheet that expects parameter values to be passed in. If you
encounter this problem, you should forego the use of precompiled stylesheets
until a fix is available.<br/><br/></li>
<li>The namespace::* axis only selects namespaces that were declared locally
on the context node. Inherited namespaces are in effect; the only known flaw is
the lack of their presence on this rarely-used axis. The name() function, when
applied to a namespace node, returns a string that disagrees with other
processors, and the XPath spec is vague on this point.<br/><br/></li>
-<li>In a multithreaded environment, some threads may lose track of xsl:key
elements.<br/><br/></li>
-<li>UTF-16 output encoding is not yet supported. Under Sun's JDK 1.2.2, a
suitable message is issued, but a stack dump occurs under JDK 1.1.8 due to
differences in ByteToCharConverter.<br/><br/></li>
<li>Implied HTML output (the output begins with <HTML>, but the output
method has not been explicitly set to HTML) is not thread-safe, due to a "late"
change of output method. <em>Workaround:</em> put an explicit <xsl:output
method="html".../> declaration in the stylesheet.<br/><br/></li>
<li>In some cases, exclude-result-prefixes takes effect even when the
specified prefix appears in sub-elements, causing output of unresolved
prefixes. If you experience this, please adjust your exclude-result-prefixes
attribute.<br/><br/></li>
<li>The id() function doesn't work in some complex match
patterns.<br/><br/></li>
<li>If you specify HTML output and encoding via xsl:output, and if a
<HEAD> element is generated, then the encoding should be represented in a
<META> tag inside the <HEAD> element. We do not put out the META
tag nor any representation of the encoding in this case.<br/><br/></li>
<li>If you are generating processing instructions (PIs) in XML output, and
you attempt to insert a literal "?>" in it, the spec says that "? >" should be
generated, inserting a space to prevent interpretation as the end of the PI. We
do not take this special step, so "?>" is generated.<br/><br/></li>
<li>When outputting URI attributes in HTML, almost all "control" characters
below decimal 32 will cause an error to be raised, rather than silently being
discarded. Most characters above decimal 127 will be output as that character.
Percent should be output as %25 at all times (it is currently output as a
literal percent); this will be fixed later.<br/><br/></li>
-<li>In a multithreaded environment, some threads may lose track of xsl:key
elements.<br/><br/></li>
<li>Need to verify which HTML element attributes should be treated as
URIs.<br/><br/></li>
</ul>
<p>Bug reports that we have not yet confirmed:</p>
@@ -20,10 +17,7 @@
<li>We have a report that passing a long string value (somewhere over 128
characters) to a template via with-param caused an overflow problem under
Solaris with a Sun JDK. We have not seen the problem under Sun's JDKs (1.1.8
and 1.2.2) on Win32. Additional reports are welcome.<br/><br/></li>
<li>We have a report that external entities can affect xsl:copy in a DOM
input scenario. An external entity that had no attributes was causing improper
copying, and adding an attribute fixed the problem. To date we have been unable
to create the bug situation in our lab.<br/><br/></li>
</ul>
- <p>Outstanding bugs are recorded in the Apache XML <jump
href="http://xml.apache.org/bugs/";>Bug Tracking System</jump>.
- If you find a bug, please use this system to report it.</p>
- <note>If the Apache XML Bug Tracking System is not working, please report
the bug to the
- <human-resource-ref idref="xalandev"/>.</note>
+ <p>The Apache XML Bug Tracking System is currently not working. If you
find a bug, please report it (with "Xalan-J 1 bug" in the subject line) to the
<human-resource-ref idref="xalandev"/>.</p>
</s3>
1.25 +19 -15 xml-xalan/xdocs/sources/xalan/DONE
Index: DONE
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/DONE,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- DONE 2000/08/23 22:08:43 1.24
+++ DONE 2000/10/13 14:55:54 1.25
@@ -1,18 +1,22 @@
-<s3 title="Changes since &xslt4j; version 1.1">
-<p>For this release, we have applied several 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>
+<s3 title="Changes since &xslt4j; version 1.2.D02">
+<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>The Xalan DTM (Document Table Model) was splitting text nodes containing
entity references into multiple nodes. We have fixed this problem, and Xalan
now treats the node as a single text node.<br/><br/></li>
-<li>Norm Walsh submitted patches enabling Xalan to accept URI substitutions
set by a custom EntityResolver.<br/><br/></li>
-<li>Gary Peskin submitted a patch enabling Xalan to process expressions with
path steps following a union. As a result, Xalan can now transform documents of
the DocBook document type.<br/><br/></li>
-<li>We now encode characters above 127 in URI attributes (in some cases
"garbage" characters were appearing). We are still soliciting input on how to
handle special URI characters between 32 and 127.<br/><br/></li>
-<li>The use of position() in sort expressions now works as expected, which
makes it easy to reverse node order.<br/><br/></li>
-<li>If a sort with the primary sort key fails completely, we no longer
perform a sort with the secondary key.<br/><br/></li>
-<li>Sergei Ivanov submitted a patch to avoid including a minus sign in an ID
in the rare case when a negative number was appearing in the ID.<br/><br/></li>
-<li>We believe we have fixed XPath retrieval of attributes qualified with a
namespace prefix. Other namespace fixes enable the name() and namespace-uri()
functions to be applied to namespace nodes.<br/><br/></li>
-<li>Ed Staub submitted a patch so that a message about processing
instruction names now appears as a warning rather than an error.<br/><br/></li>
-<li>A thread-safety issue in pattern matching was identified and
fixed.<br/><br/></li>
-<li>The output of very small decimal fractions has been
improved.<br/><br/></li>
-<li>We fixed a problem with keys that appeared when multiple threads were
using xsl:key concurrently.</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>&xslt4j; now suports UTF-16 output encoding.<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>
-<p>We also updated the build process (Ant and Make) to avoid creating a copy
of the source tree, and we placed the Ant tool in a new bin directory.</p>
+
</s3>
1.17 +1 -1 xml-xalan/xdocs/sources/xalan/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/STATUS,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- STATUS 2000/08/22 19:42:34 1.16
+++ STATUS 2000/10/13 14:55:55 1.17
@@ -12,7 +12,7 @@
<li>Reduce code size and complexity</li>
<li>Improve performance and simplify optimization.</li>
<li>Produce more localized, less-intertangled modules</li>
- <li>Begin the adoption of the <jump
href="http://trax.openxml.org/";>TRaX (Transformations for XML)</jump>
interfaces</li>
+ <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>
1.9 +2 -17 xml-xalan/xdocs/sources/xalan/commandline.xml
Index: commandline.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/commandline.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- commandline.xml 2000/05/31 15:57:46 1.8
+++ commandline.xml 2000/10/13 14:55:56 1.9
@@ -81,15 +81,11 @@
<source>-IN inputXMLURL
-XSL XSLTransformationURL
-OUT outputFileName
--LXCIN compiledStylesheetFileNameIn
--LXCOUT compiledStylesheetFileNameOut
--PARSER fully qualified class name of parser liaison
-V (Version info)
-QC (Quiet Pattern Conflicts Warnings)
-Q (Quiet Mode)
-LF (Use linefeeds only on output -- default is CR/LF)
-CR (Use carriage returns only on output -- default is CR/LF)
--INDENT (Number of spaces to indent each level in output tree --default is 0)
-TT (Trace the templates as they are being called)
-TG (Trace each result tree generation event)
-TS (Trace each selection event)
@@ -102,12 +98,8 @@
-PARAM name expression (Set a stylesheet parameter)</source>
<p>Use -IN to specify the XML source document.</p>
<p>Use -XSL to specify the XSL stylesheet file.</p>
- <p>Use -LXCIN to specify a compiled XSL stylesheet file.</p>
- <p>Use -LXCOUT to compile an XSL stylesheet for future use as -LXCIN
input.</p>
- <note>You can only use -LXCIN with a compiled stylesheet that you have
already created with the -LXOUT switch. For an
- example, see <link anchor="compiledstylesheet">Using a compiled
stylesheet</link></note>
- <p>Include -PARSER if you supply your own parser liaison class, which
is required if you do not use DTM or the
- Xerces parser.</p>
+ <p>Use -OUT to specify the output file. If you omit this flag and
argument, the processor prints the output to the
+ screen.</p>
<p>Use -TEXT if you want the output to include only element values
(not element tags with element names and
attributes).</p>
<p>Use -HTML to write 4.0 transitional HTML (some elements, such as
<br>, are
@@ -116,12 +108,5 @@
<code>TestXSLT -PARAM <ref>name expression</ref></code><br/>
To set the parameter to a string value, enclose the string in single
quotes (') to
make it an expression.</p>
- <p><anchor name="compiledstylesheet"/><em>Using a compiled
stylesheet</em></p>
- <p>If you are using a stylesheet repeatedly, you can improve
performance by compiling the stylesheet the first time
- you use it and using the compiled stylesheet for subsequent
transformations.</p>
- <p>For example, the following command line performs a transformation
and compiles the stylesheet:"<br/><br/>
- <code>java org.apache.xalan.xslt.Process -in foo.xml -xsl foo.xsl
-lxcout foo.style</code><br/><br/>
- The following command line uses the compiled stylesheet for the next
transformation:<br/><br/>
- <code>java org.apache.xalan.xslt.Process -in foo2.xml -lxcin
foo.style</code></p>
</s2>
</s1>
1.3 +18 -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.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- history.xml 2000/08/22 19:42:34 1.2
+++ history.xml 2000/10/13 14:55:57 1.3
@@ -1,3 +1,21 @@
+<s3 title="Changes for &xslt4j; version 1.2.D02">
+<p>We applied the following bug fixes</p>
+<ul>
+<li>The Xalan DTM (Document Table Model) was splitting text nodes containing
entity references into multiple nodes. We have fixed this problem, and Xalan
now treats the node as a single text node.<br/><br/></li>
+<li>Norm Walsh submitted patches enabling Xalan to accept URI substitutions
set by a custom EntityResolver.<br/><br/></li>
+<li>Gary Peskin submitted a patch enabling Xalan to process expressions with
path steps following a union. As a result, Xalan can now transform documents of
the DocBook document type.<br/><br/></li>
+<li>We now encode characters above 127 in URI attributes (in some cases
"garbage" characters were appearing). We are still soliciting input on how to
handle special URI characters between 32 and 127.<br/><br/></li>
+<li>The use of position() in sort expressions now works as expected, which
makes it easy to reverse node order.<br/><br/></li>
+<li>If a sort with the primary sort key fails completely, we no longer
perform a sort with the secondary key.<br/><br/></li>
+<li>Sergei Ivanov submitted a patch to avoid including a minus sign in an ID
in the rare case when a negative number was appearing in the ID.<br/><br/></li>
+<li>We believe we have fixed XPath retrieval of attributes qualified with a
namespace prefix. Other namespace fixes enable the name() and namespace-uri()
functions to be applied to namespace nodes.<br/><br/></li>
+<li>Ed Staub submitted a patch so that a message about processing
instruction names now appears as a warning rather than an error.<br/><br/></li>
+<li>A thread-safety issue in pattern matching was identified and
fixed.<br/><br/></li>
+<li>The output of very small decimal fractions has been
improved.<br/><br/></li>
+<li>We fixed a problem with keys that appeared when multiple threads were
using xsl:key concurrently.</li>
+</ul>
+<p>We also updated the build process (Ant and Make) to avoid creating a copy
of the source tree, and we placed the Ant tool in a new bin directory.</p>
+</s3>
<s3 title="Changes for &xslt4j; version 1.2.D01">
<p>We applied patches submitted by a number of developers to
<human-resource-ref idref="xalandev"/>.</p>
<ul>
1.10 +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.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- index.xml 2000/09/12 21:40:22 1.9
+++ index.xml 2000/10/13 14:55:58 1.10
@@ -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 developer's release incorporates a number of bug fixes,
including patches submitted to <human-resource-ref idref="xalandev"/>. One of
these patches fixes a problem that &xslt4j; was having processing documents of
the DocBook document type. 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 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>
</s2>
<s2 title="How do I get it?">
1.19 +1 -1 xml-xalan/xdocs/sources/xalan/readme.xml
Index: readme.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/readme.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- readme.xml 2000/08/23 15:26:49 1.18
+++ readme.xml 2000/10/13 14:56:00 1.19
@@ -71,7 +71,7 @@
</ul>
<s2 title="Status">
<ul>
- <li><link anchor="done">Changes since version 1.2.D01</link></li>
+ <li><link anchor="done">Changes since version 1.2.D02</link></li>
<li><link anchor="bugs">Open bugs and bug reporting</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>
1.13 +4 -0 xml-xalan/xdocs/sources/xalan/resources.xml
Index: resources.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/resources.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- resources.xml 2000/06/22 17:01:59 1.12
+++ resources.xml 2000/10/13 14:56:01 1.13
@@ -61,6 +61,10 @@
<resource id="ReadmeDocumentation" title="Release Notes"
location="readme.html"/>
<resource id="readme.xml" title="XML version of the Readme file"
location="../docs/readme.xml"/>
+ <resource id="jaxp"
+ title="Java API for XML Parsing"
+ location="http://java.sun.com/xml/docs/api/index.html"/>
+
<human-resource id="xalandev" name="Xalan Development Mailing List"
mailto="[email protected]"/>
<human-resource id="sboag" name="Scott Boag" mailto="[EMAIL PROTECTED]"/>
<human-resource id="dnbertoni" name="David N. Bertoni"
mailto="[email protected]"/>
