[
https://issues.apache.org/jira/browse/DERBY-5955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559461#comment-13559461
]
Knut Anders Hatlen commented on DERBY-5955:
-------------------------------------------
Thanks, Dag. Re 1): I was referring to DataSourceSerializationTest, which has
code similar to this in many test cases:
+ if (JDBC.vmSupportsJNDI()) {
+ final String EMBEDDED_CLASS = "EmbeddedDataSource";
+ deSerializeDs(EMBEDDED_CLASS, VERSION_10_0_2_1);
+ deSerializeDs(EMBEDDED_CLASS, VERSION_10_1_3_1);
+ deSerializeDs(EMBEDDED_CLASS, VERSION_10_2_2_0);
+ deSerializeDs(EMBEDDED_CLASS, VERSION_10_3_2_1);
+ deSerializeDs(EMBEDDED_CLASS, VERSION_10_10_1_0);
+ deSerializeDs(EMBEDDED_CLASS + _40Suffix, VERSION_10_10_1_0);
+ } else {
+ final String EMBEDDED_CLASS = "NonJNDIEmbeddedDataSource40";
+ deSerializeDs(EMBEDDED_CLASS, VERSION_10_10_1_0);
+ }
I was thinking that it might work in JNDI environment if the else branch was
made unconditional. It's not that simple in other tests, so I'm not suggesting
that we run all DataSource tests with both variants on platforms supporting
JNDI. Just that we have some minimal sanity checking if it doesn't require too
much effort.
> 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-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-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
