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=2945 *** shadow/2945 Wed Aug 1 18:28:31 2001 --- shadow/2945.tmp.2694 Wed Aug 1 19:05:03 2001 *************** *** 2,9 **** | Problem of getting of set of nodes: select="ancestor::myNode[@id='main'] | +----------------------------------------------------------------------------+ | Bug #: 2945 Product: XalanJ2 | ! | Status: ASSIGNED Version: 2.2.x | ! | Resolution: Platform: Other | | Severity: Blocker OS/Version: Other | | Priority: Other Component: Xalan | +----------------------------------------------------------------------------+ --- 2,9 ---- | Problem of getting of set of nodes: select="ancestor::myNode[@id='main'] | +----------------------------------------------------------------------------+ | Bug #: 2945 Product: XalanJ2 | ! | Status: RESOLVED Version: 2.2.x | ! | Resolution: FIXED Platform: Other | | Severity: Blocker OS/Version: Other | | Priority: Other Component: Xalan | +----------------------------------------------------------------------------+ *************** *** 62,64 **** --- 62,73 ---- is not worked!!! Parse process not cause exception. This operation worked in Xalan 2.1.0 + + ------- Additional Comments From [EMAIL PROTECTED] 2001-08-01 19:05 ------- + Bug was caused by (redundent) cloneWithReset being called from + the UnionPathIterator, and the iterator in OneStepIterator not being + reset. (Need to review: check other iterators for this.) + + Call reset on the iterator in OneStepIterator#reset. Reset the position + value in the ancestor iterator reset. Define DTMAxisIterator#cloneIterator + to not reset the iterator position, and fix the implementations of
