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:54:55 2001
--- shadow/3265.tmp.12033       Sat Aug 25 22:16:29 2001
***************
*** 2,9 ****
  | 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 |
  +----------------------------------------------------------------------------+
--- 2,9 ----
  | using xalan:evaluate in <xsl:for-each> causes 'Unknown error in XPath'     |
  +----------------------------------------------------------------------------+
  |        Bug #: 3265                        Product: XalanJ2                 |
! |       Status: RESOLVED                    Version: 2.2.x                   |
! |   Resolution: FIXED                      Platform: PC                      |
  |     Severity: Normal                   OS/Version: All                     |
  |     Priority: Other                     Component: org.apache.xalan.extens |
  +----------------------------------------------------------------------------+
***************
*** 31,33 ****
--- 31,39 ----
  ------- Additional Comments From [EMAIL PROTECTED]  2001-08-24 13:54 -------
  Created an attachment (id=447)
  test .xsl file
+ 
+ 
+ ------- Additional Comments From [EMAIL PROTECTED]  2001-08-25 22:16 -------
+ Committed VariableStack, revision 1.35, and Variable, revision 1.16 to solve 
+ this problem.  We were getting a NullPointerException when trying to use 
+ evaluate on an expression containing a top-level variable.

Reply via email to