PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3265

*** shadow/3265 Fri Aug 24 13:45:35 2001
--- shadow/3265.tmp.22248       Fri Aug 24 13:45:35 2001
***************
*** 0 ****
--- 1,24 ----
+ +============================================================================+
+ | using xalan:evaluate in <xsl:for-each> causes 'Unknown error in XPath'     |
+ +----------------------------------------------------------------------------+
+ |        Bug #: 3265                        Product: XalanJ2                 |
+ |       Status: NEW                         Version: 2.2.x                   |
+ |   Resolution:                            Platform: PC                      |
+ |     Severity: Normal                   OS/Version: All                     |
+ |     Priority: Other                     Component: org.apache.xalan.extens |
+ +----------------------------------------------------------------------------+
+ |  Assigned To: [EMAIL PROTECTED]                                     |
+ |  Reported By: [EMAIL PROTECTED]                                     |
+ |      CC list: Cc:                                                          |
+ +----------------------------------------------------------------------------+
+ |          URL:                                                              |
+ +============================================================================+
+ |                              DESCRIPTION                                   |
+ using the xalan:evaluate() extension function as select attribute in a
+ <xsl:for-each> element causes an XSLT Error with the message 'Unknown error in
+ XPath'. This seems to occure only if a string variable having another variable
+ as value is passed to the evaluate() extension.
+ I am using Xalan-J 2.2D9. With Xalan-J 2.1 its working correctly.
+ Test files follow...
+ 
+ - peter

Reply via email to