[
https://issues.apache.org/jira/browse/DERBY-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465781
]
Rick Hillegas commented on DERBY-2206:
--------------------------------------
Thanks for the quick responses, Dan. I'd like to continue the discussion of
"Setting derby.database.classpath" using the example you gave. Here's some more
detail on the problem case I had in mind:
o Suppose that there's an entry point Start_3() in the THREE jar file.
o Suppose that Start_3() calls methods in class Next.
o Suppose that there are three different versions of the Next class, one in
each of the jar files.
o Which version of the Next class gets picked up to resolve the references in
Start_3()?
It seems to me that the ANSI rules will give you the version of Next which
lives in THREE. However, the Derby rules will give you the version in ONE.
> Provide complete security model for Java routines
> -------------------------------------------------
>
> Key: DERBY-2206
> URL: https://issues.apache.org/jira/browse/DERBY-2206
> Project: Derby
> Issue Type: New Feature
> Components: Security, SQL
> Reporter: Rick Hillegas
> Fix For: 10.3.0.0
>
>
> Add GRANT/REVOKE mechanisms to control which jar files can be mined for
> user-created objects such as Functions and Procedures. In the future this may
> include Aggregates and Function Tables also. The issues are summarized on the
> following wiki page: http://wiki.apache.org/db-derby/JavaRoutineSecurity.
> Plugin management can be tracked by this JIRA rather than by DERBY-2109. This
> is a master JIRA to which subtasks can be linked.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
