Rick,
please open a JIRA issue against 2.7 and attach a complete XML/XSL
testcase. I know it is probably not much different than your description of
the problem, but a full testcase is always the best.
- Brian
- - - - - - - - - - - - - - - - - - - -
Brian Minchau
XSLT Development, IBM Toronto
e-mail: [EMAIL PROTECTED]
"If the lion purrs, it is only because it is saving you for dessert." - My
wife
"Rick Bullotta"
<[EMAIL PROTECTED]
ghthammer.com> To
<xalan-dev@xml.apache.org>
08/16/2005 10:51 cc
PM
Subject
URGENT! Broken behavior in
Please respond to xalan:evaluate extension
xalan-dev function...
Prior to the latest release, we were able to reference variables in
xalan:evaluate expressions. In particular, assume that variable $Row
references an element node that has child elements X, Y, and Z.
We then use:
<xsl:variable name="Row" select="."/>
<THING1><xsl:value-of select="xalan:evaluate(?$Row/X?)"/><THING1>
<THING2><xsl:value-of select="xalan:evaluate(?$Row/Y?)"/><THING2>
<THING3><xsl:value-of select="xalan:evaluate(?$Row/Z?)"/><THING3>
It worked fine in prior releases of Xalan, but is broken now. The second
and subsequent evaluations fail (with no exceptions/errors ? they return an
empty string or empty result). It seems like the variable reference gets
?whacked out? after its first use.
HELP!
Many thanks,
Rick Bullotta
SAP Labs, LLC
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
