Return-Path: Delivered-To: apmail-felix-dev-archive@www.apache.org Received: (qmail 30472 invoked from network); 18 Aug 2010 16:43:40 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 18 Aug 2010 16:43:40 -0000 Received: (qmail 57854 invoked by uid 500); 18 Aug 2010 16:43:39 -0000 Delivered-To: apmail-felix-dev-archive@felix.apache.org Received: (qmail 57814 invoked by uid 500); 18 Aug 2010 16:43:39 -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 57806 invoked by uid 99); 18 Aug 2010 16:43:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Aug 2010 16:43:38 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Aug 2010 16:43:38 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o7IGhIQk019255 for ; Wed, 18 Aug 2010 16:43:18 GMT Message-ID: <31404698.422751282149798173.JavaMail.jira@thor> Date: Wed, 18 Aug 2010 12:43:18 -0400 (EDT) From: "Richard S. Hall (JIRA)" To: dev@felix.apache.org Subject: [jira] Commented: (FELIX-2532) bundle-symbolic-name constraint is not handled by the OBR resolver In-Reply-To: <19472684.234761281366796179.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FELIX-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899905#action_12899905 ] Richard S. Hall commented on FELIX-2532: ---------------------------------------- There are a couple issues here: 1. I believe that OBR doesn't handle implicit attributes (i.e., bundle-symbolic-name and bundle-version) on exported packages at all. The proposed patch is only a partial solution for this limitation, e.g., it doesn't address bundle-version. 2. The proposed patch is not really correct either, since it simply replaces the implementation-specific system bundle name with the generic one (i.e., system.bundle), but what happens if someone is importing it with the implementation name? For system bundle, there actually needs to be a special case where this attribute is multi-valued. > bundle-symbolic-name constraint is not handled by the OBR resolver > ------------------------------------------------------------------ > > Key: FELIX-2532 > URL: https://issues.apache.org/jira/browse/FELIX-2532 > Project: Felix > Issue Type: Bug > Components: Bundle Repository (OBR) > Affects Versions: bundlerepository-1.6.4 > Reporter: Arjun Panday > Priority: Critical > Attachments: DataModelHelperImpl.java > > > I have a bundle importing javax.xml.bind specifically from the system.bundle. The import looks like this: > Import-Package: javax.xml.bind;bundle-symbolic-name=system.bundle > Bindex translates the import into the following requirement: > > Import package javax.xml.bind > > This requirement is not resolved by the RepositoryAdmin service. > When I loop over resolver.getUnsatisfiedRequirements(), I log: > Unsatisfied OBR requirement (&(package=javax.xml.bind)(bundle-symbolic-name=system.bundle)(mandatory:<*bundle-symbolic-name)) > It seems that the bundle-symbolic-name constraint is not handled by the resolver. > /arjun -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.