db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4978) Document the new SQLPermission required by the JDBC 4.1 Connection.abort(Executor) method
Date Tue, 25 Jan 2011 16:15:44 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986481#action_12986481
] 

Kim Haase commented on DERBY-4978:
----------------------------------

Thanks, Rick, I'll go with that writeup, then. 

By "the existing policy files" I guess you mean our example ones. So people could grant one
set of permissions to derby.jar, another set to derbyclient.jar, and so on.

The GlassFish policy file gives blanket permissions to all the jars, but I guess that makes
sense for the app server (as opposed to a user application):

// Derby driver classes get all permissions by default
grant codeBase "file:${com.sun.aas.derbyRoot}/lib/-" {
    permission java.security.AllPermission;
}; 

> Document the new SQLPermission required by the JDBC 4.1 Connection.abort(Executor) method
> -----------------------------------------------------------------------------------------
>
>                 Key: DERBY-4978
>                 URL: https://issues.apache.org/jira/browse/DERBY-4978
>             Project: Derby
>          Issue Type: Task
>          Components: Documentation, JDBC
>    Affects Versions: 10.8.0.0
>            Reporter: Rick Hillegas
>            Assignee: Kim Haase
>
> We need to add material to the Reference and Developer's Guides as described in the 2011-01-14
comment on DERBY-4869.

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