Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Message-ID: <2084253253.1232398619657.JavaMail.jira@brutus>
Date: Mon, 19 Jan 2009 12:56:59 -0800 (PST)
From: "Richard S. Hall (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Subject: [jira] Commented: (FELIX-884) OBR should expose registered services
 as capabilities of local repository
In-Reply-To: <91877379.1232279579571.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-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665225#action_12665225 ] 

Richard S. Hall commented on FELIX-884:
---------------------------------------

Should we be creating the union of Export-Service and getRegisteredServices() for the service capabilities of the bundle? I think it currently would create duplicates, no?

Also, what is the relationship between this patch and 887? Is there a dependency such that one needs to be applied before the other? It seems like they are conflicting.

> OBR should expose registered services as capabilities of local repository
> -------------------------------------------------------------------------
>
>                 Key: FELIX-884
>                 URL: https://issues.apache.org/jira/browse/FELIX-884
>             Project: Felix
>          Issue Type: Improvement
>          Components: Bundle Repository (OBR)
>    Affects Versions: bundlerepository-1.2.0
>            Reporter: Felix Meschberger
>         Attachments: FELIX-884-2.patch, FELIX-884.patch
>
>
> The OBR implementation exposes the current state of the framework as a Repository, the LocalRepository. This provides the installed bundles as parts provided by a repository with their capabilities. These capabilities do not currently only reflect the currently installed set of bundles and their static setup such as package import/export and service import/export. The actually registered services, though are not exposed as capabilities whatsoever.
> So if for example, the OPS4J Pax Web Service bundle registers an HttpService instance. But this fact is not reflected by a ExportService header. Trying to install a bundle from the OBR which requires an HttpService fails, since the actually registered HttpService is not provided as a capability.
> I suggest, the LocalRepository exposes all registered services (just their names would probably do it) as capabilities of the system bundle. This is not entirely correct but should probably be enough to satisfy the requirements of bundles.
> WDYT ?
> Ref: Discussion on user list at http://markmail.org/message/ivkdvhpk4gclkylv

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