DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18008>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18008 NullPointerException while using key() function ------- Additional Comments From [EMAIL PROTECTED] 2004-02-19 18:23 ------- DTM philosophical review: The real problem here seems to be that "ni" and "nodes" aren't bound to the right evaluation context (specifically, they can't obtain the correct DTM Manager) and thus aren't able to use the DTM Node Handle ("pos") to look up the DTM object which contains that node. You're solving that by bypassing these node iterators, which sorta works as a patch... but my question is why the iterator wasn't configured properly in the first place. If this operation is supposed to work and doesn't, that's a problem waiting to bite our ankles later on. So I'd lean toward fixing the node-iterator objects rather than working around them. Having said that, if you're forced to do a work-around, asking the XPath Context for its DTM Manager is at least semantically reasonable...
