You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Matt Benson (JIRA)" <ji...@apache.org> on 2018/05/10 21:48:00 UTC

[jira] [Resolved] (WEAVER-25) Reject blueprint methods that access entities that would be inaccessible

     [ https://issues.apache.org/jira/browse/WEAVER-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Benson resolved WEAVER-25.
-------------------------------
    Resolution: Fixed

31583df219f3fb66ea9d362b2ef99b0a3120b789

> Reject blueprint methods that access entities that would be inaccessible
> ------------------------------------------------------------------------
>
>                 Key: WEAVER-25
>                 URL: https://issues.apache.org/jira/browse/WEAVER-25
>             Project: Commons Weaver
>          Issue Type: Improvement
>          Components: privilizer
>    Affects Versions: 1.4
>            Reporter: Matt Benson
>            Assignee: Matt Benson
>            Priority: Major
>             Fix For: 1.4
>
>
> ...from the _importing_ type, i.e. classes, constructors, methods other than other {{static}} methods from the same class whose import is cascaded
> Blueprint methods access fields, but the rest imply the import of arbitrary whole types which is at least a slippery slope... choose your own metaphor. The safest course is to reject these. One immediate implication is that a valid blueprint method may not instantiate an anonymous type.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)