Rick, could you please open a defect for this in bugzilla against XalanJ2. Please attach xml/xsl files. Without a testcase we can't say if this is a bug or not. Thanks, ---------- Brian Minchau XSLT Development, IBM Toronto e-mail: [EMAIL PROTECTED] -----Original Message----- From: Rick Bullotta [mailto:[EMAIL PROTECTED] Sent: Friday, July 09, 2004 12:53 PM To: [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
