You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2014/06/23 14:55:24 UTC

[jira] [Resolved] (DERBY-6624) Use javax.xml.xpath interfaces for XPath support

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

Knut Anders Hatlen resolved DERBY-6624.
---------------------------------------

          Resolution: Fixed
       Fix Version/s: 10.11.0.0
    Issue & fix info:   (was: Patch Available)

Thanks, Bryan. I've committed the patch to trunk, and filed DERBY-6633 to simplify the documentation as well. I also noticed that we're lacking some test coverage in SqlXmlUtil.java, so I've filed DERBY-6634 to improve the tests.

> Use javax.xml.xpath interfaces for XPath support
> ------------------------------------------------
>
>                 Key: DERBY-6624
>                 URL: https://issues.apache.org/jira/browse/DERBY-6624
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.11.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>             Fix For: 10.11.0.0
>
>         Attachments: d6624-1a.diff
>
>
> Currently, Derby uses the interfaces in the org.w3c.dom.xpath package to implement XPath support. That package is not part of the Java SE specification. Even though the package is included as an internal API in some of the major Java runtimes, using the standard javax.xml.xpath package instead would be better. It would be more portable, and less likely to break in the future if JVM vendors remove the internal API.



--
This message was sent by Atlassian JIRA
(v6.2#6252)