Wrong node count in CachedXPathAPI.eval() function?

[Rick Bullotta <ri...@lighthammer.com>]

Reposting for comments.

Thanks!


-----Original Message-----
From: Rick Bullotta [mailto:rick.bullotta@lighthammer.com] 
Sent: Friday, July 09, 2004 12:53 PM
To: xalan-dev@xml.apache.org
Subject: Possible bug in Xpath API/eval function?

Seems that the eval() function in the CachedXPathAPI object returns an
incorrect result if the result is a nodeset/nodelist.  It appears to always
return "one node short".  If the Xpath expression would evaluate to a
nodeset of 60 nodes, the resulting XNodeSet only has 59 when cast to a
nodelist.  If the Xpath expression would evaluate to a single node, the
XNodeSet has zero when cast to a nodelist.

Any wisdom/guidance welcomed!

Rick Bullotta
CTO
Lighthammer Software (http://www.lighthammer.com)


---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org