[ http://issues.apache.org/jira/browse/DERBY-942?page=all ]
Anurag Shekhar updated DERBY-942:
---------------------------------
Attachment: derby-942.diff
This patch is meant only for review. Because of bug in current version of
jdk1.6 (mustang) ResultSet.getType after closing connection resulting in
exception while network client. Embedded driver uses a light weight check for
all the methods which doesn't checks for connection in this call.
I have set the noSecurityManager to true for testing this feature.
Default implementation of QueryObjectGenerator uses reflection check the
DataObject before invokeing setters. Reflection being privileged operation
fails when called with default security manager.
Description of patch
java/engine/org/apache/derby/jdbc/EmbeddedDataSource40.java
java/client/org/apache/derby/jdbc/ClientDataSource40.java
added code to call DefaultQueryGenerator
added code to return null for getQueryObjectGenerator to indicate this
jdbc doesn't have QueryObjectGenerator and relies on the default implementation.
java/engine/org/apache/derby/impl/jdbc/EmbedConnection40.java
java/client/org/apache/derby/client/net/NetConnection40.java
added code to call DefaultQueryGenerator
build.xml
added additinla target to uncomment jdbc4 class name listed in
tools/jar/extraDBMSclasses.properties if the build is made with jdbc4 support
tools/jar/extraDBMSclasses.properties
added entry for EmbeddedDataSource40 so that it it gets added to derby.jar
(right now its not getting added to this)
> Add JDBC4 Ease of Development Support
> -------------------------------------
>
> Key: DERBY-942
> URL: http://issues.apache.org/jira/browse/DERBY-942
> Project: Derby
> Type: New Feature
> Components: JDBC
> Reporter: Rick Hillegas
> Assignee: Anurag Shekhar
> Fix For: 10.2.0.0
> Attachments: derby-942.diff
>
> As described in the JDBC 4 spec, sections 20.1, 20.2, and 3.1.
> The Ease of Development extensions provide a way to create tabular DataSets
> from queries and tuple signatures. The jdk ships with a factory for creating
> these DataSets, which is a class which implements the QueryObjectGenerator
> interface. A database can write its own custom QueryObjectGenerator, or just
> ship with the default, jdk-shipped version. For this task, we will simply
> wire the default jdk-shipped factory into the appropriate methods:
> Connection.createQueryObject() and DataSource.createQueryObject().
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
