[
https://issues.apache.org/jira/browse/JEXL-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16806906#comment-16806906
]
Henri Biestro commented on JEXL-292:
------------------------------------
Controlling the Uberspect permitted methods paves the way to a fine control
over what can be called from scripts.
> Allow to specify custom Permissions class for Uberspect to be used later by
> Introspector
> ----------------------------------------------------------------------------------------
>
> Key: JEXL-292
> URL: https://issues.apache.org/jira/browse/JEXL-292
> Project: Commons JEXL
> Issue Type: New Feature
> Affects Versions: 3.1
> Reporter: Dmitri Blinov
> Priority: Minor
>
> As of now the default implementation of {{internal.introspection.Uberspect}}
> class does not allow the usage of anything other than default instance of
> {{internal.introspection.Permissions}} class, althow internally the
> {{internal.introspection.Introspector}} has a constructor that accesspts the
> {{Permissions}} object. Subclassing of {{Uberspect}} does not help here since
> {{Uberspect.base()}} method is decalred {{final}}. We need some way to pass
> customized {{Permissions}} class to default {{Uberspect}} implementation
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
