db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-538) Investigate using the standard java.net.URLClassLoader for database class loading.
Date Fri, 01 Jun 2007 18:25:15 GMT

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


Mime
View raw message