db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-537) SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR fail when running with a SecurityManager enabled.
Date Mon, 25 Jun 2007 22:35:25 GMT

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

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

    Attachment: derby-537_10.2_diff.txt

This is a port of DERBY-537 and DERBY-538 to 10.2.  Changes ported were 387324,473416,473440,473780,473828,473834,474376,482812,482850,483108,483148,483160,483738,484722,543524
Enabled dblook_test.java with security manager to test installation of jar with security manager.
I am running derbyall now and will commit tomorrow if all goes well. 

Kathey



> 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: Kathey Marsden
>             Fix For: 10.3.0.0
>
>         Attachments: derby-537_10.2_diff.txt, derby-537_10.2_stat.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.


Mime
View raw message