You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2018/01/16 17:11:00 UTC

[jira] [Comment Edited] (ARIES-1761) ensure we inject BundleContext to the beans which need it

    [ https://issues.apache.org/jira/browse/ARIES-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16327392#comment-16327392 ] 

Guillaume Nodet edited comment on ARIES-1761 at 1/16/18 5:10 PM:
-----------------------------------------------------------------

I'm not sure to understand the purpose.

The interface javadoc specifies that in most cases, beans should not need to implement this interface.  Furthermore, if a bean actually implements it, we'd need to also provide the class else an NoClassDefFoundException would be thrown.


was (Author: gnt):
I'

> ensure we inject BundleContext to the beans which need it
> ---------------------------------------------------------
>
>                 Key: ARIES-1761
>                 URL: https://issues.apache.org/jira/browse/ARIES-1761
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>    Affects Versions: blueprint-spring-0.5.0
>            Reporter: Freeman Fang
>            Priority: Major
>         Attachments: ARIES-1761.patch
>
>
> With the old spring-dm, there's a "BundleContextAware" interface, any bean implements this interface can get BundleContext injected.
> With the new aries-blueprint-spring, we should follow similar pattern, like check if a bean has setBundleContext method, if so, just inject the BundleContext into the bean, so that the application bundles with work with spring-dm can also work with aries-blueprint-spring



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