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 10:49:13 +0000 (UTC)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12629835.1359518630305.272508.1360579753524@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=13575724#comment-13575724 ] 

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

Dag is correct. DERBY-5880 made the suffix-less data sources more capable, and the javadoc comments were updated to reflect the new reality. The suffix-less data sources can (still) be used on JDBC 3.0 platforms, but now they also support the full JDBC 4.0 API. The data sources with the "40" suffix require at least JDBC 4.0 support in the JVM, otherwise the classes will fail to load. They support the full JDBC 4.1 API.

I guess we should add a sentence to the javadoc of the 40-suffixed classes to say that they will also work on Java SE 6/JDBC 4.0. They will have to continue supporting that platform for backward compatibility reasons, and we could just as well say that explicitly in the javadoc. That might make the naming less confusing too.
                
> 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