db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5955) Prepare Derby to run with Compact Profiles (JEP 161)
Date Tue, 15 Jan 2013 01:38:12 GMT

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

Dag H. Wanvik updated DERBY-5955:

    Attachment: derby-5955-make-tests-run-01.stat

Uploading patch derby-5955-make-tests-run-01. This patch only makes changes to the tests to
make them run on a platform with Profile == compact2.

I have verified these changes make the regressions run without error on my early build of
the JEP 161 codeline (with patch derby-5955-add-cp2-to-jars) and also that the tests still
run ok on an ordinary Java SE platform.

There is, however, one little product change: ij has undocumented functionality to support
script based testing of XA, cf xaHelper#getXADataSource. This code has now been changed to
work even when JNDI is absent by using the new data sources.

The tests for serailizable data sources introduce new binary checked in lobs, so to test this
patch you need to either generate the new lobs yourself (cd to directory java/testing/org/apache/derbyTesting/functionTests/testData/serializedDataSources,
then run org.apache.derbyTesting.functionTests.testData.serializedDataSources.SerializeDataSources
with no arguments. this will produce the new lobs containing serialized data sources at level
10_10), or you can download the zip bundle I attach, "derby-5955-ser-b.zip" and unzip it from
the top level in the repo. See also DERBY-5997.

I don't expect people to build and test Java 8 with the new profiles code; please check the
patch for coorrectness as to existing tests not being brolen by this patch. Thanks!

> Prepare Derby to run with Compact Profiles (JEP 161)
> ----------------------------------------------------
>                 Key: DERBY-5955
>                 URL: https://issues.apache.org/jira/browse/DERBY-5955
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation, JDBC, Services, SQL
>            Reporter: Dag H. Wanvik
>            Assignee: Dag H. Wanvik
>         Attachments: apidiff.zip, client-graph.png, derby-5955-add-cp2-to-jars.diff,
derby-5955-client-restructure-01.diff, derby-5955-client-restructure-01.stat, derby-5955-client-restructure-02-delta.diff,
derby-5955-client-restructure-02.diff, derby-5955-client-restructure-02.stat, derby-5955-embed-restructure-01.diff,
derby-5955-embed-restructure-01.stat, derby-5955-embed-restructure-02.diff, derby-5955-embed-restructure-02.stat,
derby-5955-embed-restructure-03.diff, derby-5955-embed-restructure-03.stat, derby-5955-embed-restructure-04.diff,
derby-5955-embed-restructure-04.stat, derby-5955-embed-restructure-followup.diff, derby-5955-embed-restructure-followup.stat,
derby-5955-make-tests-run-01.diff, derby-5955-make-tests-run-01.stat, derby-5955-new-non-jndi-ds-01.diff,
derby-5955-new-non-jndi-ds-01.stat, derby-5955-new-non-jndi-ds-02.diff, derby-5955-new-non-jndi-ds-02.stat,
derby-5955-proof-of-concept-2.diff, derby-5955-proof-of-concept-2.stat, derby-5955-proof-of-concept.diff,
derby-5955-proof-of-concept.stat, derby-5955-ser.zip, embedded-graph.png, old-client-graph.png,
old-embedded-graph.png, publishedapi.zip, publishedapi.zip
> While waiting for a Java module system (aka project Jigsaw), it has been decided to define
a few subsets of the Java SE Platform Specification, cf JEP 161 ( http://openjdk.java.net/jeps/161).
> A quote from the JEP: "More broadly, this feature is intended to enable the migration
of applications currently built on top of the Java ME Connected Device Configuration (CDC)
to appropriate Profiles of the Java SE Platform, part of the long-term effort to converge
CDC with Java SE."
> It would be good if we make Derby to run on such limited profiles. The current proposal
places JDBC in Compact Profile 2 (cf. link above), while other libraries used by Derby, e.g.
javax.naming (JNDI) are in Profile 3 (larger).
> It would be good if Derby could run on the smallest posible platform, i.e. Profile 2,
but that will probably involve some changes to make Derby gracefully limit functionality when
some libraries are missing.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message