[
https://issues.apache.org/jira/browse/DERBY-5955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567796#comment-13567796
]
Rick Hillegas commented on DERBY-5955:
--------------------------------------
Thanks for checking in those changes, Dag. Some comments on the public api
javadoc:
--------------------------------
ClientConnectionPoolDataSource
ClientDataSource
ClientXADataSource
EmbeddedConnectionPoolDataSource
EmbeddedDataSource
EmbeddedXADataSource
"Java SE 7 og higher" -> "Java SE 7 or higher"
--------------------------------
ClientConnectionPoolDataSource40
ClientDataSource40
ClientXADataSource40
EmbeddedConnectionPoolDataSource40
EmbeddedDataSource40
EmbeddedXADataSource40
Replace "running on full Java SE 7, corresponding to JDBC 4.1." onward with
this:
"running on the following platforms:
o JDBC 4.1 - Java SE 7
o JDBC 4.2 - full Java SE 8
Use $alternativeCP2DataSource if your application runs on Java 8 compact
profile 2.
Use $alternativeJDBC4.0DataSource if your application runs on the following
platforms:
o JDBC 4.0 - Java SE 6
o JDBC 3.0 - J2SE 5.0"
--------------------------------
I think that the above changes will fix the package overview for the jdbc4
version of org.apache.derby.jdbc. Right now the jdbc 4 DataSources only say
that they are appropriate for Java SE 7. After the above changes, those
DataSources should indicate that they are also appropriate for Java SE 8.
Thanks,
-Rick
> 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: JDBC, Services, SQL
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Fix For: 10.10.0.0
>
> 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-javadoc.diff,
> derby-5955-javadoc.status, derby-5955-make-tests-run-01.diff,
> derby-5955-make-tests-run-01.stat, derby-5955-make-tests-run-02.diff,
> derby-5955-make-tests-run-02.stat, derby-5955-make-tests-run-03.diff,
> 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-rename.diff, derby-5955-ser-b.zip, 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
