DO NOT REPLY [Bug 14221] New: - org.w3c.dom.xpath.XPathEvaluator.evaluate differs from spec

[bu...@apache.org]

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=14221>.
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=14221

org.w3c.dom.xpath.XPathEvaluator.evaluate differs from spec

           Summary: org.w3c.dom.xpath.XPathEvaluator.evaluate differs from
                    spec
           Product: XalanJ2
           Version: 2.4
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: org.apache.xpath
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: richard.zschech@cqrdata.com


Hi,

Ive been using the dom3 xpath packages for a while now by writing a wrapper around xalan's xpath package.

Now that you've included it in xalan I decided to try yours. But it seems that the definition of the method org.w3c.dom.xpath.XPathEvaluator.evaluate(...) and org.w3c.dom.xpath.XPathExpression.evaluate(...) takes an Object as its last parameter and returns an Object also.

According to the spec http://www.w3.org/TR/DOM-Level-3-XPath/java-binding.html these should be XPathResults. Ive also noticed the same issue in xerces.

Where have you got your version of the spec from?
Is it safe to cast the results of these methods to an XPathResult?

Thanks in advance,
>From Richard.