Hi Frank,
Brian Minchau is working on merging the serializers for the Xalan-J
Interpretive and Compiled processors. I believe this bug will be fixed by
that work, and have assigned the bug report to him.
The xsl:value-of element actually creates a text node, so it's not an
error for a stylesheet to compute xsl:value-of within an xsl:attribute.
To answer your question, there is active development going on in both
Xalan-J Interpretive and Compiled (XSLTC) processors.
I hope that helps.
Thanks,
Henry
------------------------------------------------------------------
Henry Zongaro Xalan development
IBM SWS Toronto Lab Tie Line 969-6044; Phone (905) 413-6044
mailto:[EMAIL PROTECTED]
Frank Karlstr�m <[EMAIL PROTECTED]>
03/05/2003 05:36 AM
Please respond to xalan-dev
To: <[EMAIL PROTECTED]>
cc:
Subject: XSLTC bug.
Hello all. This is my first post to this list, so dont bite me if
I have not done all of my homework.
I am currently migrating from Xalan to Xalan/XSLTC, and found a bug.
After searching BugZilla, I found that someone has already filed that
bug.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15481
This is a bug in XSLTC, according to the XSLT spec.
http://www.w3.org/TR/xslt#creating-attributes
The following are all errors:
...
Creating nodes other than text nodes during the instantiation of the
content of the xsl:attribute element; implementations may either signal
the error or ignore the offending nodes.
So from the example:
xml:
<a><![CDATA[">&]]></a>
with the xslt:
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"; version="1.0">
<xsl:output method='html' indent='yes'/>
<xsl:template match='/'>
<a>
<xsl:attribute name="href"><xsl:value-of select="/a"
/></xsl:attribute></a>
</xsl:template>
</xsl:stylesheet>
That should either have been signaled as an error, or ignored if the CDATA
section
had not been a CDATA section. but since it is, XSLTC outputs it is
uniterpreted chars,
wich would have been correct if the output was'nt supposed to be in an
attribute value.
I havent been poking so much into the XSLTC code yet, so if someone on
this list could lead me in the right direction, I could start looking for
the cause of the bug, and create a patch for it, if someone else hasnt
started to fix it.
BTW, are all development currently done on Xalan, or is someone actively
developing on XSLTC
too?
Best regards Frank Karlstr�m
**********************************************************************
Senior Java-programmer and developer
Confirm AS
Mail: [EMAIL PROTECTED]
**********************************************************************
