db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anurag Shekhar (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-942) Add JDBC4 Ease of Development Support
Date Fri, 24 Feb 2006 17:49:39 GMT
     [ 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

Description of patch
	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.

	added code to call DefaultQueryGenerator 

added additinla target to uncomment jdbc4 class name listed in tools/jar/extraDBMSclasses.properties
if the build is made with jdbc4 support

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:
>  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:
For more information on JIRA, see:

View raw message