Return-Path: X-Original-To: apmail-felix-dev-archive@www.apache.org Delivered-To: apmail-felix-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 30D6A434C for ; Mon, 23 May 2011 13:42:33 +0000 (UTC) Received: (qmail 97199 invoked by uid 500); 23 May 2011 13:42:31 -0000 Delivered-To: apmail-felix-dev-archive@felix.apache.org Received: (qmail 97126 invoked by uid 500); 23 May 2011 13:42:31 -0000 Mailing-List: contact dev-help@felix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@felix.apache.org Delivered-To: mailing list dev@felix.apache.org Received: (qmail 97035 invoked by uid 99); 23 May 2011 13:42:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 May 2011 13:42:31 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 May 2011 13:42:29 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 3BE46D9038 for ; Mon, 23 May 2011 13:41:48 +0000 (UTC) Date: Mon, 23 May 2011 13:41:48 +0000 (UTC) From: "Guest (JIRA)" To: dev@felix.apache.org Message-ID: <717089125.35972.1306158108242.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1726576705.35956.1306158107374.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Updated] (FELIX-2968) Bind method of optional references can be called before bind methods of mandatory references MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/FELIX-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guest updated FELIX-2968: ------------------------- Description: Hi, i got the following problem. I've some references to services, some of them are mandatory and some are optional. Well now osgi/scr waits to call the bind methods till all mandatory services are available. However when it starts to call the bind methods it seems that it doesn't care if those are mandatory or optional. This can result in a not expected behavior where optional dependencies are satisfied before the mandatory are. Consider you have a optional dynamic multiple service binding which you want to use with a mandatory service. There's as far as it looks to me no way to ensure that the mandatory binds are called before optional are allowed. was: Hi, i got the following problem. I've some references to services, some of them are mandatory and some are optional. Well now osgi/scr waits to call the bind methods till all mandatory services are available. However when it starts to call the bind methods it seams that it doesn't care if those are mandatory or optional. This can result in a not expected behavior where optional dependencies are satisfied before the mandatory are. Consider you have a optional dynamic multiple service binding which you want to use with a mandatory service. There's as far as it looks to me no way to ensure that the mandatory binds are called before optional are allowed. > Bind method of optional references can be called before bind methods of mandatory references > -------------------------------------------------------------------------------------------- > > Key: FELIX-2968 > URL: https://issues.apache.org/jira/browse/FELIX-2968 > Project: Felix > Issue Type: Bug > Components: Declarative Services (SCR) > Affects Versions: scr-1.6.0 > Reporter: Guest > Labels: felix, scr > Original Estimate: 1h > Remaining Estimate: 1h > > Hi, > i got the following problem. > I've some references to services, some of them are mandatory and some are optional. Well now osgi/scr waits to call the bind methods till all mandatory services are available. > However when it starts to call the bind methods it seems that it doesn't care if those are mandatory or optional. This can result in a not expected behavior where optional dependencies are satisfied before the mandatory are. > Consider you have a optional dynamic multiple service binding which you want to use with a mandatory service. There's as far as it looks to me no way to ensure that the mandatory binds are called before optional are allowed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira