[
https://issues.apache.org/jira/browse/DERBY-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-930:
Derby Info: (was: [Existing Application Impact])
Add support for autoloading of Derby client
[ http://issues.apache.org/jira/browse/DERBY-930?page=all ]
Rick Hillegas updated DERBY-930:
Derby Info: [Existing Application Impact] (was: [Existing Application
Impact, Release Note Needed])
Since this issue was fixed, no release note is needed.
[ http://issues.apache.org/jira/browse/DERBY-930?page=all ]
Kathey Marsden updated DERBY-930:
-
Derby Info: [Existing Application Impact, Release Note Needed] (was:
[Regression, Existing Application Impact, Release Note Needed])
DERBY-1459 is logged
[ http://issues.apache.org/jira/browse/DERBY-930?page=all ]
Kathey Marsden updated DERBY-930:
-
Attachment: autoloading_scenarios.html
The attached document autoloading_scenarios.html has three scenarios that need
to be considered for our autoloading
[ http://issues.apache.org/jira/browse/DERBY-930?page=all ]
Kathey Marsden updated DERBY-930:
-
Derby Info: [Existing Application Impact, Release Note Needed]
This change may impact existing applications as evidenced by the need to
change a related
[ http://issues.apache.org/jira/browse/DERBY-930?page=all ]
Rick Hillegas updated DERBY-930:
Attachment: bug930_rev3.diff
Attaching bug930_rev3.diff, which makes a small change to the test for whether
we're running with jar files. Build 81 of jdk1.6
[ http://issues.apache.org/jira/browse/DERBY-930?page=all ]
Mike Matrigali updated DERBY-930:
-
Component: Build tools
JDBC
Add support for autoloading of Derby client drivers
---
[ http://issues.apache.org/jira/browse/DERBY-930?page=all ]
Rick Hillegas updated DERBY-930:
Attachment: bug930_rev2.diff
I have attached a revised patch for this feature: bug930_rev2.diff. This patch
cannot be committed until mustang build 81 posts.
[ http://issues.apache.org/jira/browse/DERBY-930?page=all ]
Rick Hillegas updated DERBY-930:
Attachment: ClassloadingTest.jar
I have attached a jarred up experiment which demonstrates a
SecurityManager-induced classloading issue which results in the
[ http://issues.apache.org/jira/browse/DERBY-930?page=all ]
Rick Hillegas updated DERBY-930:
Attachment: bug930_problem2.diff
The next attachment (bug930_problem2.diff) shows that the problem is not in
Derby's drivers. The problem occurs with a
[ http://issues.apache.org/jira/browse/DERBY-930?page=all ]
Rick Hillegas updated DERBY-930:
Attachment: bug930_problem.diff
I have attached bug930_problem.diff, which demonstrates the problem I am having
autoloading Derby drivers under a
11 matches
Mail list logo
