Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Mon, 11 Feb 2013 15:03:13 +0000 (UTC)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12629835.1359518630305.273022.1360594993090@arcas>
In-Reply-To: <JIRA.12629835.1359518630305@arcas>
References: <JIRA.12629835.1359518630305@arcas>
Subject: [jira] [Commented] (DERBY-6059) Document Derby usage running on
 Java 8 JEP 161 Compact Profiles
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13575821#comment-13575821 ] 

Knut Anders Hatlen commented on DERBY-6059:
-------------------------------------------

Hi Kim,

You're right, the 40 classes are not required for Java 7. They are only required if you call the getParentLogger() method, which was new in JDBC 4.1. Since our implementation of that method always throws SQLFeatureNotSupportedException, I don't think it's very likely that our users will have applications that depend on that method.

So we have the plain (unsuffixed) data sources that can be used on Java SE 5 and newer, as long as you stick to the JDBC 4.0 subset of the API. And the "40" classes can be used on Java SE 6 and newer, as long as you stick to the JDBC 4.1 subset of the API (or possibly JDBC 4.2, as I don't think any new methods are planned in the data sources for 4.2).
                
> Document Derby usage running on Java 8 JEP 161 Compact Profiles
> ---------------------------------------------------------------
>
>                 Key: DERBY-6059
>                 URL: https://issues.apache.org/jira/browse/DERBY-6059
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Dag H. Wanvik
>            Assignee: Kim Haase
>             Fix For: 10.10.0.0
>
>         Attachments: javadoc-snapshot.pdf
>
>
> Document that Derby can run even under constrained Java runtime as planned for Java 8 Compact Profiles 2 and 3 (not 1, the smallest runtime, since it has no JDBC). Cf work in DERBY-5955 which made Derby run gracefully even when some normal Java runtime packages are missing, notably JNDI and JMX.
> That work introduced six new data sources which have reduced functionality compared with the corresponding ones for full Java SE, in that there is no JNDI support. The six new data sources are for the client driver:
> Client/server data sources for use with Java 8 Compact Profile 2 and above:
>     BasicClientDataSource40 - Data source
>     BasicClientConnectionPoolDataSource40 - Connection pooling data source
>     BasicClientXADataSource40 - XA data source 
> Embedded data sources for use with Java 8 Compact Profile 2 and above:
>     BasicEmbeddedDataSource40 - Data source
>     BasicEmbeddedConnectionPoolSource40 - Connection pooling data source
>     BasicEmbeddedXASource40 - XA data source 

--
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