felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Custine (JIRA)" <j...@apache.org>
Subject [jira] Updated: (FELIX-32) Implement mechanisms for accessing "all" service references
Date Thu, 25 Jan 2007 05:33:49 GMT

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

Chris Custine updated FELIX-32:

    Attachment: FELIX-32.diff

This patch implements the getAllServiceReferences method in BundleContextImpl.  In the process
of implementing this, I refactored the getServiceReferences code to use the same basic utility
function for filtering the service references and moved that utility to the main Felix framework
class to centralize the functionality similar to previous patches.

> Implement mechanisms for accessing "all" service references
> -----------------------------------------------------------
>                 Key: FELIX-32
>                 URL: https://issues.apache.org/jira/browse/FELIX-32
>             Project: Felix
>          Issue Type: New Feature
>          Components: Framework, Specification compliance
>            Reporter: Richard S. Hall
>         Attachments: FELIX-32.diff
> This issue is described in section 5.9 of the OSGi R4 specification. The main jist of
this issue is that R4 allows multiple versions of the same package to be shared in the framework
at the same time. This means that the framework must dynamically partition the service registry
based on package versions (e.g., a bundle using log v1, should not see a log v2 service).
To support bundles that want to inspect all services regardless of package version, new API
was defined in R4 for such purposes. This API includes BundleContext.getAllServiceReferences()
as well as a new AllServiceListener.
> Most of the plumbing for all of this works correctly in Felix now, but these last two
API aspects still need to be implemented. Their implementation should be pretty straightforward.

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

View raw message