[ http://issues.apache.org/jira/browse/DERBY-1075?page=all ]
Deepa Remesh updated DERBY-1075:
--------------------------------
Attachment: loader.java
I have written a small java program 'loader.java' to test that I can load
different version of derby classes using a classloader. After loading a
particular version of Derby, I get a connection and check the product version
in the connection metadata. I found that I can switch between versions without
problems. I also checked that the classloader ignores the settings in the class
path and uses only what is specified in the program. So all the following
commands result in same output:
1. java -classpath . loader C:\deepa\Derby\10.1\classes
C:\deepa\Derby\trunk\classes
2. java -classpath .;C:\deepa\Derby\10.1\classes loader
C:\deepa\Derby\10.1\classes C:\deepa\Derby\trunk\classes
3. java -classpath .;C:\deepa\Derby\trunk\classes loader
C:\deepa\Derby\10.1\classes C:\deepa\Derby\trunk\classes
However, I found I cannot use DriverManager to get a connection. The reason I
think is this statement from the javadoc "When the method getConnection is
called, the DriverManager will attempt to locate a suitable driver from amongst
those loaded at initialization and those loaded explicitly using the same
classloader as the current applet or application.". Use of DataSource to get
connection works fine. I hope it is okay to proceed by using DataSource. I
would appreciate if someone can take a quick look at the attached program and
let me know if this is the right direction.
> Combine the script and the test available for upgrade testing into a java test
> ------------------------------------------------------------------------------
>
> Key: DERBY-1075
> URL: http://issues.apache.org/jira/browse/DERBY-1075
> Project: Derby
> Type: Sub-task
> Reporter: Deepa Remesh
> Assignee: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: loader.java
>
> Separating a part of DERBY-514 into a sub-task. This sub-task is to combine
> the script 'runphases.ksh' and the java file 'phaseTester.java' into a single
> java test. This will help to later add the upgrade tests into the regression
> suite. Also, this sub-task can be done independent of DERBY-1049 which is
> blocking DERBY-514.
--
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
