[
https://issues.apache.org/jira/browse/DERBY-5955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13554323#comment-13554323
]
Rick Hillegas commented on DERBY-5955:
--------------------------------------
Hi Dag,
Thanks for all of this great work. A big +1 to what you've done so far.
Since you're working on tests now, I assume you're basically done with
restructuring the DataSources in the product. I have built the javadoc and
looked at the DataSource public api. It looks to me like the correct classes
are included in the public api. In addition, it looks like the DataSources
implement the expected interfaces. I see that you've introduced a number of
interfaces which don't appear in the public api. It's too bad that they are
still mentioned by the interface lists for the included DataSources--but I
don't know how to make the cruft disappear from those lists.
When you come up for air, it would be good to give users guidance about which
DataSource best fits their environment. I think these are the environments we
can expect:
o Embedded application running on CDC/FP 1.1
o Embedded application running on Java 5.
o Embedded application running on Java 6 and 7
o Embedded application running on full Java 8
o Embedded application running on CP2, the small device configuration for Java
8.
o Client/server application running on Java 5.
o Client/server application running on Java 6 and 7
o Client/server application running on full Java 8
o Client/server application running on CP2, the small device configuration for
Java 8.
The following adjustments to the public api documentation make sense to me:
o Adjust the wording of the lead sentence in the javadoc header for every
DataSource, indicating which of the above environments it fits. The first
sentence appears in the package overview, in the generated table of classes
included in the package.
o Adjust the package overview html, adding the new DataSources to the list of
DataSources. Probably you will need 2 more blocks of DataSources, parallel to
the existing 2 blocks.
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: 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-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
