[
https://issues.apache.org/jira/browse/DERBY-6239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893496#comment-13893496
]
Rick Hillegas commented on DERBY-6239:
--------------------------------------
Hi Kim,
I don't think we need to document deregisterDriver for the client policy file.
The permission is not needed by Derby code. The permission may be needed by
other client components. If so, then I think it should be discussed by the user
documentation for those components. Thanks.
> Document optional permission SQLPermission("deregisterDriver")
> --------------------------------------------------------------
>
> Key: DERBY-6239
> URL: https://issues.apache.org/jira/browse/DERBY-6239
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.10.1.4, 10.11.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Kim Haase
> Fix For: 10.10.1.4, 10.11.0.0
>
> Attachments: DERBY-6239-2.diff, DERBY-6239-2.stat, DERBY-6239-2.zip,
> DERBY-6239-3.diff, DERBY-6239.diff, DERBY-6239.stat, DERBY-6239.zip,
> tadminnetservbasic.html
>
>
> See DERBY-6224.
> The documentation should mention the need for
> SQLPermission("deregisterDriver") during system shutdown on Java SE 8 and
> higher. The permission is only needed by derby.jar. It's an optional
> permission, only needed if system shutdown is invoked without the
> deregister=false attribute.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
