You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <de...@db.apache.org> on 2005/08/24 21:01:08 UTC
[jira] Created: (DERBY-538) Investigate using the standard java.net.URLClassLoader for database class loading.
Investigate using the standard java.net.URLClassLoader for database class loading.
----------------------------------------------------------------------------------
Key: DERBY-538
URL: http://issues.apache.org/jira/browse/DERBY-538
Project: Derby
Type: Sub-task
Reporter: Daniel John Debrunner
Assigned to: Daniel John Debrunner
Would change the fix for DERBY-537) so that's why it is a sub-task.
Use of the standard class loader would reduce security concerns and allow jars stored in the database to take advantage of standard features such as package sealing.
--
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
[jira] Closed: (DERBY-538) Investigate using the standard
java.net.URLClassLoader for database class loading.
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel John Debrunner closed DERBY-538.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.3.0.0
Due to issues with the standard URLClassLoader I decided to continue with Derby's own JarLoader but extend it from SecureClassLoader.
This then will allow Derby's class loader to implement features such as package sealing.
Commit 543524 switched the parent class. Believe there is no more work to do under this issue.
Sealing and other security features can be added separately.
> Investigate using the standard java.net.URLClassLoader for database class loading.
> ----------------------------------------------------------------------------------
>
> Key: DERBY-538
> URL: https://issues.apache.org/jira/browse/DERBY-538
> Project: Derby
> Issue Type: Sub-task
> Components: Services
> Reporter: Daniel John Debrunner
> Assignee: Daniel John Debrunner
> Fix For: 10.3.0.0
>
>
> Would change the fix for DERBY-537) so that's why it is a sub-task.
> Use of the standard class loader would reduce security concerns and allow jars stored in the database to take advantage of standard features such as package sealing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-538) Investigate using the standard
java.net.URLClassLoader for database class loading.
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-538?page=all ]
Mike Matrigali updated DERBY-538:
---------------------------------
Component: Services
> Investigate using the standard java.net.URLClassLoader for database class loading.
> ----------------------------------------------------------------------------------
>
> Key: DERBY-538
> URL: http://issues.apache.org/jira/browse/DERBY-538
> Project: Derby
> Type: Sub-task
> Components: Services
> Reporter: Daniel John Debrunner
> Assignee: Daniel John Debrunner
>
> Would change the fix for DERBY-537) so that's why it is a sub-task.
> Use of the standard class loader would reduce security concerns and allow jars stored in the database to take advantage of standard features such as package sealing.
--
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
[jira] Commented: (DERBY-538) Investigate using the standard
java.net.URLClassLoader for database class loading.
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-538?page=comments#action_12456267 ]
Daniel John Debrunner commented on DERBY-538:
---------------------------------------------
Java bug 4950148 means that the closing of the jar file opened by URClassLoader is delayed until that object's GC, which can cause issues for tests which try to cleanup after a database shutdown.
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4950148
Seem to hit this bug if I use this class loader, also seen in DatabaseClassLoadingTest for the testDatabaseInClasspath() which uses URLClassLoader. Once the test is complete and the database shutdown, the jar file cannot be removed from the file system on windows. Need to inviestigate more as to what is going on.
> Investigate using the standard java.net.URLClassLoader for database class loading.
> ----------------------------------------------------------------------------------
>
> Key: DERBY-538
> URL: http://issues.apache.org/jira/browse/DERBY-538
> Project: Derby
> Issue Type: Sub-task
> Components: Services
> Reporter: Daniel John Debrunner
> Assigned To: Daniel John Debrunner
>
> Would change the fix for DERBY-537) so that's why it is a sub-task.
> Use of the standard class loader would reduce security concerns and allow jars stored in the database to take advantage of standard features such as package sealing.
--
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