[
https://issues.apache.org/jira/browse/DERBY-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000393#comment-13000393
]
Knut Anders Hatlen commented on DERBY-2739:
-------------------------------------------
> Why wouldn't derby use the xml factories so that the choice of transformer
> can be done at runtime?
Hi Dave,
That's exactly what it does after the changes made in this issue. The
transformer is now created by calling
TransformerFactory.newInstance().newTransformer().
> Use DOM interfaces to implement XML operators
> ---------------------------------------------
>
> 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
> Fix For: 10.8.0.0
>
> Attachments: infinity-NaN.diff, ns-npe.diff, numeric-tests.diff,
> releaseNote.html, remove-xalan-jars.diff, stricter-assertions.diff,
> xml-interfaces-2.diff, xml-interfaces-3.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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
