felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FELIX-2647) Implement Coordinator Service
Date Mon, 30 Dec 2013 10:41:50 GMT

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

Carsten Ziegeler resolved FELIX-2647.

    Resolution: Fixed

The implementation now passed the TC including security checks.
Logging is not widely used yet and could be improved

> Implement Coordinator Service
> -----------------------------
>                 Key: FELIX-2647
>                 URL: https://issues.apache.org/jira/browse/FELIX-2647
>             Project: Felix
>          Issue Type: New Feature
>          Components: Coordinator Service, Specification compliance
>            Reporter: Felix Meschberger
>            Assignee: Carsten Ziegeler
>             Fix For: coordinator-1.0.0
> The OSGi R 4.3 draft 2 foresees the specification of a new Coordinator Service supporting
a light-weight transaction-like functionality. Apache Felix should have an implementation
of this service to be able to support the extension of the Configuration Admin service which
depends on the Coordinator service.
> The Apache Felix implementation will obey the Provisional OSGi API policy [1] by renaming
the exports as follows:
>    org.osgi.jmx.service.coordination ==> org.apache.felix.jmx.service.coordination
>    org.osgi.service.coordination ==> org.apache.felix.service.coordination
> and marking the exports with the mandatory attribute status="provisional" as well as
marking all interfaces/classes deprecated.
> For full details see the OSGi R 4.3 draft 2 available from http://www.osgi.org/Download/File?url=/download/osgi-4.3-early-draft2.pdf
> [1] http://felix.apache.org/site/provisional-osgi-api-policy.html

This message was sent by Atlassian JIRA

View raw message