You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2010/10/10 22:26:30 UTC
[jira] Updated: (FELIX-2647) Implement Coordinator Service
[ https://issues.apache.org/jira/browse/FELIX-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated FELIX-2647:
-------------------------------------
Component/s: Coordinator Service
Description:
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
was:
The OSGi R 4.3 draft 2 foresees the specification of a new Coordination 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 Coordination 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
Summary: Implement Coordinator Service (was: Implement Coordination Service)
> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.