[
https://issues.apache.org/jira/browse/DERBY-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-2739:
--------------------------------------
Attachment: stricter-assertions.diff
XMLTypeAndOpsTest has many negative test cases that expect compile-time errors.
However, these tests use assertStatementError(), which doesn't care whether the
error happens at compile-time or during execution. The attached patch
(stricter-assertions.diff) changes many calls from assertStatementError() to
assertCompileError() so that we'll detect if a change moves the error from
compile-time to run-time.
Committed revision 1055031.
> 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,
> stricter-assertions.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.
