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

Rick Hillegas commented on DERBY-4869:
--------------------------------------

All righty then. My previous comment was a little muddled. This is the shape of 
something that actually works:

1) SQLPermission( "callAbort" ) must be granted to derby.jar and to 
derbyclient.jar. Note, however, that Derby's implementations of abort(Executor) 
are not wrapped in doPrivileged blocks. That means that outer (application) 
code domains are NOT absolved of the need to be granted this permission also. 
The application designer controls who can call this method by only granting 
this permission to tools used by superusers.

2) Our JDBC documentation in the Reference Guide should explain the need to 
grant this permission both to Derby and to the superuser tools.

3) We will need to make similar statements in the Developer's Guide in the 
section titled "Running Derby under a security manager".

> Implement JDBC 4.1, the api increment introduced by Java 7
> ----------------------------------------------------------
>
>                 Key: DERBY-4869
>                 URL: https://issues.apache.org/jira/browse/DERBY-4869
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>            Reporter: Rick Hillegas
>         Attachments: derby-4869-01-ac-rs-getObject.diff, 
> derby-4869-01-ad-rs-getObject.diff, derby-4869-02-aa-cs-ps-addBatch.diff, 
> derby-4869-02-ab-cs-ps-addBatch.diff, 
> derby-4869-03-aa-rs-getObject-errorCleanup.diff, 
> derby-4869-04-aa-rs-getObject-simplification.diff, 
> derby-4869-05-aa-rs-getObject-exception.diff, 
> derby-4869-06-aa-cs-getObject.diff, derby-4869-06-ab-cs-getObject.diff, 
> derby-4869-07-aa-timedisplacement.diff, derby-4869-08-ac-nullHandling.diff, 
> derby-4869-exp-01-aa-noTryCatch.diff, disable-tests.diff, 
> JDBC_4.1_Changes.html, timezone.diff
>
>
> This is a master issue logged to track our work implementing JDBC 4.1, the 
> changes to the java.sql and javax.sql packages introduced by Java 7.

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

Reply via email to