Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Message-ID: <1443289676.1238355290532.JavaMail.jira@brutus>
Date: Sun, 29 Mar 2009 12:34:50 -0700 (PDT)
From: "Marcel Offermans (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Subject: [jira] Work started: (FELIX-987) Please make bundle context
 injection optional
In-Reply-To: <1931387608.1237305652131.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Work on FELIX-987 started by Marcel Offermans.

> Please make bundle context injection optional
> ---------------------------------------------
>
>                 Key: FELIX-987
>                 URL: https://issues.apache.org/jira/browse/FELIX-987
>             Project: Felix
>          Issue Type: Improvement
>          Components: Dependency Manager
>            Reporter: Jeroen van Grondelle
>            Assignee: Marcel Offermans
>            Priority: Minor
>
> We use the dependency manager to defer the registration of some services till required services are available
> through binding an intermediary object to the dependency manager.
> As we want to bind these services using a specific bundle context, we communicate this bundle context
> through the intermediary.
> Dependency manager's default behaviour is to inject the bundle context associated with the manager in any
> member of type bundle context. Thus, our bundle context is overwritten and our services are bound to the
> wrong bundle context.
> Could bundle context  injection be made optional through a parameter/setting?
> Thanks in advance!

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