Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Tue, 12 Feb 2013 13:41:13 +0000 (UTC)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12629835.1359518630305.277828.1360676473551@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=13576616#comment-13576616 ] 

Rick Hillegas commented on DERBY-6059:
--------------------------------------

Java 8 will increase the number of JDBC methods which are only available from the 40 data sources. So the distinction is becoming more important for portable applications.

I can see that this is tricky to document and puzzling to users. Maybe we could help users by adding the following factory methods to, say, EmbeddedDriver and ClientDriver:

public static javax.sql.DataSource getDataSource()

public static javax.sql.ConnectionPoolDataSource() getConnectionPoolDataSource()

public static javax.sql.XADataSource getXADataSource()

Thanks,
-Rick


> 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