dleslie 00/11/29 14:49:55
Modified: xdocs/sources/xalan BUGS DONE index.xml
Log:
Fix for serialization bug setting paramters
with compiled stylesheets.
Revision Changes Path
1.15 +0 -1 xml-xalan/xdocs/sources/xalan/BUGS
Index: BUGS
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/BUGS,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- BUGS 2000/10/13 15:29:09 1.14
+++ BUGS 2000/11/29 22:49:43 1.15
@@ -2,7 +2,6 @@
<p>Open bugs:</p>
<ul>
<li>When format-number() should format NaN or infinity, it generates the
wrong string if default strings are used. <em>Workaround:</em> 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>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>
1.39 +1 -1 xml-xalan/xdocs/sources/xalan/DONE
Index: DONE
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/DONE,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- DONE 2000/11/29 15:52:29 1.38
+++ DONE 2000/11/29 22:49:45 1.39
@@ -1,4 +1,5 @@
<s3 title="Changes since &xslt4j; version 1.2.1">
+<p>Dmitry Voytenko submitted a fix for a bug (a "not serializable
exception") that occurred when attempting to set stylesheet parameters with a
compiled stylesheet. Accordingly, it is now possible to compile a stylesheet
with the command-line utility -lxcin flag and then perform a transformation
with it and set a parameter using the -lxcout and param -flags. See <link
idref="commandline" anchor="compiledstylesheet">Using a compiled
stylesheet</link>.</p>
<p>When you use an XSLTProcessor object to perform multiple transformations,
you must reset the XSLTProcessor between each transformation. The existing
<jump
href="apidocs/org/apache/xalan/xslt/XSLTProcessor.html#reset()">reset()</jump>
method (with no arguments) also clears all stylesheet parameters that you have
set with either of the <jump
href="apidocs/org/apache/xalan/xslt/XSLTProcessor.html#setStylesheetParam(java.lang.String,
org.apache.xalan.xpath.XObject)">setStylesheetParam()</jump> methods. In
response to requests for more control over resetting stylesheet parameters, we
have added two methods:</p>
<ul>
<li>The XSLTProcessor <jump
href="apidocs/org/apache/xalan/xslt/XSLTProcessor.html#reset(boolean)">reset(boolean
resetParams)</jump> method lets you specify whether stylesheet parameters are
to be reset.<br/><br/>
@@ -6,6 +7,5 @@
<li>The XSLTProcessor <jump
href="apidocs/org/apache/xalan/xslt/XSLTProcessor.html#resetTopLevelParams()">resetTopLevelParams()</jump>
method clears stylesheet parameter settings without performing a general reset
of the XSLTProcessor.</li>
</ul>
-
<p>If you run across a problem with &xslt4j;, we strongly encourage you to
write a patch and submit it to <human-resource-ref idref="xalandev"/>. 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>
1.16 +2 -2 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.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- index.xml 2000/11/28 21:58:05 1.15
+++ index.xml 2000/11/29 22:49:46 1.16
@@ -64,8 +64,8 @@
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 provides you with direct control over whether
XSLTProcessor stylesheet parameter settings are cleared between
- transformations. For the details, see <link idref="readme">Release
Notes</link>.</p>
+ <p>This release fixes a bug setting parameters with a compiled stylesheet
and provides you with direct control
+ over whether XSLTProcessor stylesheet parameter settings are cleared
between transformations. For the details, see <link idref="readme">Release
Notes</link>.</p>
</s2>
<s2 title="How do I get it?">
