db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-5095) Update XML operator documentation to reflect new requirements
Date Mon, 07 Mar 2011 16:02:00 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003406#comment-13003406
] 

Kim Haase commented on DERBY-5095:
----------------------------------

Thanks, Knut, for noticing this problem and fixing it.

> Update XML operator documentation to reflect new requirements
> -------------------------------------------------------------
>
>                 Key: DERBY-5095
>                 URL: https://issues.apache.org/jira/browse/DERBY-5095
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.8.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>             Fix For: 10.8.0.0
>
>         Attachments: cdevstandardsxml.html, derby-5095-1a.diff
>
>
> The developer's guide mentions the classpath requirements for using the XML operators:
http://db.apache.org/derby/docs/dev/devguide/cdevstandardsxml.html
> After DERBY-2739, this section is a bit out of date and the following should be updated:
> 1) "For the XML operators to work properly, Derby requires that a JAXP parser, such as
Apache Xerces, and Apache Xalan are included in the Java classpath."
> Since we're no longer using Xalan directly, we shouldn't state that Apache Xalan must
be in the classpath. We could for example replace "Apache Xalan" in the above sentence with
"and a DOM Level 3 XPath implementation, such as Apache Xalan,".
> 2) "After JVM version 1.4, Sun renamed the JAXP packages. Derby cannot find these renamed
packages."
> This is no longer true. Derby can now find the required packages on newer Sun JVMs (at
least on Java 6 and newer).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message