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 "Kathey Marsden (JIRA)" <ji...@apache.org> on 2007/07/05 14:52:05 UTC

[jira] Updated: (DERBY-537) SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR fail when running with a SecurityManager enabled.

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

Kathey Marsden updated DERBY-537:
---------------------------------

    Assignee: Daniel John Debrunner  (was: Kathey Marsden)

> SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR fail when running with a SecurityManager enabled.
> --------------------------------------------------------------------------------------
>
>                 Key: DERBY-537
>                 URL: https://issues.apache.org/jira/browse/DERBY-537
>             Project: Derby
>          Issue Type: Bug
>          Components: Security, SQL
>    Affects Versions: 10.1.1.0
>            Reporter: Daniel John Debrunner
>            Assignee: Daniel John Debrunner
>             Fix For: 10.1.3.2, 10.2.2.1, 10.3.0.0
>
>         Attachments: derby-537_10.2_diff.txt, derby-537_10.2_stat.txt, derby-537_10_1_diff.txt
>
>
> Seen if running the lang/dcl.sql test with a SecurityManager. Accessing the jar file is not within a priviledged block.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.