[
https://issues.apache.org/jira/browse/DERBY-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463743
]
Daniel John Debrunner commented on DERBY-2224:
----------------------------------------------
I think these are symtoms of the fact that Foundation 1.1 introduces BigDecimal
but the Derby code is not set up to handle it correctly with JSR 169.
Derby's JSR 169 support (which does not have the set/getBigDecimal methods)
was written against Foundation 1.0 which does not have BigDecimal and thus
makes that assumption. So a combination of JSR169 and BigDecimal was not
anticipated. I'll add some notes to DERBY-2210 and enter a new bug.
> Test harness should support J2ME 1.1
> ------------------------------------
>
> Key: DERBY-2224
> URL: https://issues.apache.org/jira/browse/DERBY-2224
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.2.0, 10.3.0.0
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Attachments: DERBY_2224_harness.diff, DERBY_2224_tests.diff
>
>
> I would like to enable the 'old' test harness to support the new version of
> IBM's j2ME implementation, which is based on j2ME jdk spec version 1.1. This
> is available with a product named Websphere Everyplace Micro Edition 6.1.
> from IBM.
> We already support j9_foundation, which matches to j2ME jdk spec 1.0. I'd
> like to add j9_foundation11, which then matches to j2ME jdk spec 1.1.
> I'm proposing to switch my automated tests over to the newer version going
> forward, and to minimize complexity of the change, I'd like to make the
> canons reflect behavior of the new version. The differences are minimal.
> However, I want to be able to still run with the old (except where the
> results differ, failures would occur with the old version).
> One of the reasons for moving to the new version is that there is a bug with
> the older version in regards to security manager, preventing a smooth run of
> the junit tests, and I'd like to run all short-running tests (suites.All and
> derbyall) with at least one of the versions. Another reason is that the j2ME
> spec 1.0 is really old.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
