[ http://issues.apache.org/jira/browse/DERBY-930?page=all ]

Rick Hillegas updated DERBY-930:
--------------------------------

    Attachment: bug930.diff

This patch makes the jar building targets stuff a) derby.jar with the embedded 
driver name and b) derbyclient.jar with the client driver name. Some details 
follow:

o trunk/build.xml - Created a single target for making the META-INF directory. 
Previously, this logic was cut-and-pasted across the jarring targets.

o trunk/build.xml - Added logic to create META-INF/services/java.sql.Driver 
files to derby.jar and derbyclient.jar

o AutoloadTest.java - New test to verify that the Derby drivers autoload when 
run from our jar files.

I disabled the security manager for AutoloadTest. The reasons for this are 
documented in AutoloadTest_app.properties: When running under our test harness 
from jar files under jdk1.6, system properties can't be read. This causes the 
drivers to silently fail to autoload. Note that when running under jdk1.6 from 
jar files outside our test harness, the drivers correctly autoload.

The new test is wired into the jdbc4 suite. The suite runs cleanly under 1.6 
against the class tree and against the Derby jar files. The test itself runs 
cleanly embedded and with the Derby client under 1.6 and 1.4 and against the 
class tree and the jar files.

Here are the patch contents:

A      
java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\jdbcapi
A      
java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\jdbcapi\AutoloadTest_app.properties
A      
java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\jdbcapi\AutoloadTest.java
A      
java\testing\org\apache\derbyTesting\functionTests\tests\junitTests\jdbcapi\build.xml
M      java\testing\org\apache\derbyTesting\functionTests\suites\jdbc4.runall
M      
java\testing\org\apache\derbyTesting\functionTests\util\DerbyJUnitTest.java
M      
java\testing\org\apache\derbyTesting\functionTests\util\derby_tests.policy
M      java\testing\build.xml
M      build.xml

> Add support for autoloading of Derby client drivers
> ---------------------------------------------------
>
>          Key: DERBY-930
>          URL: http://issues.apache.org/jira/browse/DERBY-930
>      Project: Derby
>         Type: New Feature
>     Reporter: Rick Hillegas
>     Assignee: Rick Hillegas
>  Attachments: bug930.diff
>
> Write Derby's driver names into the correct spot in derby.jar and 
> derbyclient.jar so that the 1.6 vm autoloads Derby drivers. Section 10.2.1 of 
> the JDBC4 spec describes the details.

-- 
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

Reply via email to