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-2040) Setting derby.database.classpath to contain installed jars causes the database to be unbootable when a Securitymanager is installed.
Date Fri, 01 Jun 2007 18:27:15 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel John Debrunner closed DERBY-2040.
----------------------------------------

    Resolution: Fixed

Revision: 543565 means that installing/replacing/droping jars and loading classes works with
a security manager as demonstrated by DatabaseClassLoadingTest.

> Setting derby.database.classpath to contain installed jars causes the database to be
unbootable when a Securitymanager is installed.
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2040
>                 URL: https://issues.apache.org/jira/browse/DERBY-2040
>             Project: Derby
>          Issue Type: Bug
>          Components: Security, Services
>    Affects Versions: 10.2.1.6
>            Reporter: Daniel John Debrunner
>            Assignee: Daniel John Debrunner
>             Fix For: 10.3.0.0
>
>
> If the jars are sucessfully installed (without a security manager see DERBY-537) and
the class path set then subsequent boots with a security manager fail with a SecurityException
due to trying to install a class loader.
> Related to DERBY-537 but not the same.

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