[ 
https://issues.apache.org/jira/browse/DERBY-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Knut Anders Hatlen updated DERBY-2739:
--------------------------------------

    Attachment: ns-npe.diff

Here's a test case for the previously mentioned issue with 
PrefixResolverDefault. The comments in the code mentioned that we'd get NPEs if 
we didn't have a prefix resolver, but none of the tests failed if the resolver 
was removed. The attached patch (ns-npe.diff) exposes this problem by executing 
an XPath query that contains a function call prefixed by a namespace.

The expected result in the test case is a failure during compilation of the 
query, and that's exactly what we see. If the PrefixResolverDefault object 
isn't provided, though, the query is compiled successfully. Instead, it fails 
during execution with a NullPointerException hidden deep down in its exception 
chain.

The changes in the xml-interfaces.diff patch don't make this test case fail, 
even though it doesn't explicitly provide a resolver, so it looks like we don't 
need any special handling of this problem in the new code.

Committed the new test case to trunk with revision 1054991.

> Automatically detect and use the Xalan which is included in Sun's Java 1.5.0 
> and higher
> ---------------------------------------------------------------------------------------
>
>                 Key: DERBY-2739
>                 URL: https://issues.apache.org/jira/browse/DERBY-2739
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.3.1.4
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>         Attachments: infinity-NaN.diff, ns-npe.diff, numeric-tests.diff, 
> xml-interfaces.diff
>
>
> Sun's Java 1.5.0 and higher includes Xalan, but Derby doesn't find it because 
> it has been moved to a non-standard package. Derby should be able to detect 
> and use these classes if it cannot find Xalan in the standard package on the 
> classpath. This would make it easier for many users to start using Derby's 
> XML features.
> See also the discussion in this thread: 
> <URL:http://mail-archives.apache.org/mod_mbox/db-derby-dev/200705.mbox/%[email protected]%3e>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to