Return-Path: Delivered-To: apmail-felix-dev-archive@www.apache.org Received: (qmail 29961 invoked from network); 17 Sep 2007 09:30:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Sep 2007 09:30:57 -0000 Received: (qmail 63580 invoked by uid 500); 17 Sep 2007 09:30:47 -0000 Delivered-To: apmail-felix-dev-archive@felix.apache.org Received: (qmail 63520 invoked by uid 500); 17 Sep 2007 09:30:47 -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 63469 invoked by uid 99); 17 Sep 2007 09:30:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Sep 2007 02:30:47 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Sep 2007 09:32:44 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 194C6714035 for ; Mon, 17 Sep 2007 02:30:32 -0700 (PDT) Message-ID: <21782161.1190021432098.JavaMail.jira@brutus> Date: Mon, 17 Sep 2007 02:30:32 -0700 (PDT) From: "Felix Meschberger (JIRA)" To: dev@felix.apache.org Subject: [jira] Created: (FELIX-366) Bound Service Replacement incorrect MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Bound Service Replacement incorrect ----------------------------------- Key: FELIX-366 URL: https://issues.apache.org/jira/browse/FELIX-366 Project: Felix Issue Type: Bug Components: Declarative Services Reporter: Felix Meschberger Currently SCR implements incorrect bound service replacement for references of unary cardinality: Instead of first binding the new (replacement) service and then unbinding the old (outgoing) service, the old service is first unbound and then the replacement bound. This violates the specification in section 112.5.10, Bound Service Replacement, of the Declarative Services Specification. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.