[
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-new-non-jndi-ds-01.stat
derby-5955-new-non-jndi-ds-01.diff
Attaching patch derby-5955-new-non-jndi-ds-01. This introduces the six (three
for each driver) new data source that are not dependent on JNDI.
Details:
M
java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/DataSourceTest.java
This includes a small sanity check by adding a test case to be run even on full
Java SE.
Adaptations of tests to make them run on a compact profile 2 JRE will follow
later. The focus here is the new sources of the data source classes.
Also it adds changes to the following files:
M java/engine/org/apache/derby/iapi/services/info/JVMInfo.java
Add utility method to determine if JNDI is available.
M java/drda/org/apache/derby/impl/drda/XADatabase.java
Make this class fall back to using the non-jndi version if running without JNDI.
M java/engine/org/apache/derby/modules.properties
Remove the requirement that JNDI classes be present for Derby to boot.
M tools/jar/dnc.properties
Add new data sources to client jar.
M tools/jar/extraDBMSclasses.properties
Add new data sources to embedded jar
M tools/javadoc/publishedapi_jdbc4.ant
Add new data source classes to published API.
Running regressions.
> 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-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-new-non-jndi-ds-01.diff, derby-5955-new-non-jndi-ds-01.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
