You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2003/02/21 17:58:29 UTC
DO NOT REPLY [Bug 6285] -
XSLTInfo.properties 'version' is quite confusing
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6285>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6285
XSLTInfo.properties 'version' is quite confusing
------- Additional Comments From mcnamara@ca.ibm.com 2003-02-21 16:58 -------
I'd like to take a stab at fixing this.
XSLTInfo.properties currently contains an entry:
version=2.4.1
At first glance one might expect that if you try
<xsl:value-of select="system-property('xsl:version')"/>
you would get back the value specified in the XSLTInfo.properties file
similarly as you do when you try
<xsl:value-of select="system-property('xsl:vendor')"/> or
<xsl:value-of select="system-property('xsl:vendor-url')"/>
But this is not the case, and *should not* be the case because
<xsl:value-of select="system-property('xsl:version')"/> should return the
version of XSLT implemented by the processor. The processor currently returns
the value 1 since org/apache/xpath/functions/FuncSystemProperty.java disregards
the value in XSLTInfo.properties and returns XNumber(1.0). There's a separate
issue being tracked under Bugzilla 7660 that deals with the processor returning
the value 1 instead of 1.0, but I'll leave that alone for now!
So, it seems that the code is ignoring the value in XSLTInfo.properties and the
value is incorrect anyways. In XSLT 2.0, there are new system-property values
being proposed, namely xsl:product-name and xsl:product-version, but we'll have
to wait until our XSLT 2.0 implementation to use these.
I propose that we change XSLTInfo.properties so that
version=1.0
and that we add a comment line to indicate the product version number. This
comment can be updated automatically by the Ant's filtering capability at build
time as Shane suggests.
I'll attach a patch for consideration.