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 "Mike Matrigali (JIRA)" <de...@db.apache.org> on 2006/01/23 21:21:13 UTC
[jira] Updated: (DERBY-538) Investigate using the standard
java.net.URLClassLoader for database class loading.
[ 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