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=2878

*** shadow/2878 Mon Jul 30 06:37:45 2001
--- shadow/2878.tmp.23965       Mon Jul 30 06:54:18 2001
***************
*** 2,9 ****
  | XPath crashes under XalanJ 2.2.D8                                          |
  +----------------------------------------------------------------------------+
  |        Bug #: 2878                        Product: XalanJ2                 |
! |       Status: ASSIGNED                    Version: 2.2.x                   |
! |   Resolution:                            Platform: Other                   |
  |     Severity: Normal                   OS/Version: Other                   |
  |     Priority: Other                     Component: org.apache.xpath        |
  +----------------------------------------------------------------------------+
--- 2,9 ----
  | XPath crashes under XalanJ 2.2.D8                                          |
  +----------------------------------------------------------------------------+
  |        Bug #: 2878                        Product: XalanJ2                 |
! |       Status: RESOLVED                    Version: 2.2.x                   |
! |   Resolution: FIXED                      Platform: Other                   |
  |     Severity: Normal                   OS/Version: Other                   |
  |     Priority: Other                     Component: org.apache.xpath        |
  +----------------------------------------------------------------------------+
***************
*** 78,80 ****
--- 78,86 ----
  ------- Additional Comments From [EMAIL PROTECTED]  2001-07-29 23:08 
-------
  Created an attachment (id=365)
  JAVA program to demonstrate this bug...
+ 
+ 
+ ------- Additional Comments From [EMAIL PROTECTED]  2001-07-30 06:54 -------
+ DTMDefaultBase#getNextNamespaceNode and DTMDefaultBase#getFirstNamespaceNode 
+ were sometimes returning a node without the DTM identity bits set.  Fixed in 
+ latest CVS.

Reply via email to