[
https://issues.apache.org/jira/browse/DERBY-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576625#comment-13576625
]
Kristian Waagan commented on DERBY-6059:
----------------------------------------
> 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:
While this may help in some cases, note that configuring systems using data
sources often consists of specifying the data source class as a text string.
As such I think it is important that we document this as good as we can.
> 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
