[
https://issues.apache.org/jira/browse/DERBY-6239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792453#comment-13792453
]
Knut Anders Hatlen commented on DERBY-6239:
-------------------------------------------
Thanks for picking this up, Kim.
I think the release note attached to DERBY-6224 is probably the best place to
go if you need a description of the behaviour with or without the permission on
different versions of the JVM.
Maybe it should also have a short mentioning or a cross-reference in
[deregister=false
attribute|http://db.apache.org/derby/docs/10.10/ref/rrefattribderegister.html],
since deregister=true will have no effect if derby.jar doesn't have the
permission.
And possibly we could put "if permitted" or something after "deregister the
JDBC driver" in [shutdown=true
attribute|http://db.apache.org/derby/docs/10.10/ref/rrefattrib16471.html].
> 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.3, 10.11.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Kim Haase
>
> 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#6144)
