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 "Kathey Marsden (JIRA)" <ji...@apache.org> on 2008/07/25 19:37:31 UTC

[jira] Updated: (DERBY-2228) Support Derby on J2ME/CDC/Foundation 1.1

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

Kathey Marsden updated DERBY-2228:
----------------------------------

    Component/s: Store
                 SQL
                 Services
                 JDBC

> Support Derby on J2ME/CDC/Foundation 1.1
> ----------------------------------------
>
>                 Key: DERBY-2228
>                 URL: https://issues.apache.org/jira/browse/DERBY-2228
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Services, SQL, Store
>    Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.1.4
>            Reporter: Daniel John Debrunner
>            Assignee: Daniel John Debrunner
>             Fix For: 10.2.3.0, 10.3.1.4
>
>
> Derby works on J2ME/CDC/Foundation 1.0 with JSR 169 and thus should also be able to run on Foundation 1.1since Foundation 1.1 is backwards compatible.
> However the additon of BigDecimal breaks an assumption made in the Foundation 1.0 implementation, see DERBY-2224 and DERBY-2210 for details.
> I think simple changes that ensure the CDC data factory is booted rather than the J2SE data factory should fix any issues with a Foundation 1.1 platform.
> I think currently the J2SE data factory is being booted becase BigDecimal exists, when in reality it requires BigDecimal and JDBC 2 or higher.
> This big is not intended to take advantage of new features in Foundation 1.1, that is handled by DERBY-2210.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.