[jira] Resolved: (ARIES-531) Allow field injection in some cases with the Blueprint extender's permissions

["Valentin Mahrwald (JIRA)" <ji...@apache.org>]

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

Valentin Mahrwald resolved ARIES-531.
-------------------------------------

    Resolution: Fixed

Changes committed in #1055827.

> Allow field injection in some cases with the Blueprint extender's permissions
> -----------------------------------------------------------------------------
>
>                 Key: ARIES-531
>                 URL: https://issues.apache.org/jira/browse/ARIES-531
>             Project: Aries
>          Issue Type: Improvement
>          Components: Blueprint
>            Reporter: Valentin Mahrwald
>            Assignee: Valentin Mahrwald
>
> Currently, Blueprint uses the joint permissions of the Blueprint bundle and the Blueprint extender bundle to perform any kind of privileged actions like property injection, service retrieval and field injection.
> However, this permission scheme does not work that well with field injection because usually a Blueprint bundle would not need to (and probably should not) have ReflectPermission. Especially, if all that the field injection is used for is something relatively common like injecting a PersistenceContext ...
> So with this issue a slightly more relaxed scheme will be introduced where:
> - field injection for fields in classes that reside in the Blueprint bundle itself is done with the permissions of the Blueprint extender
> - all other field injections uses joint permissions as before

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.