felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven E. Harris (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-2950) [Framework] Adopt OSGi R4.3 API as framework internal API
Date Mon, 28 Nov 2011 16:01:40 GMT

    [ https://issues.apache.org/jira/browse/FELIX-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158527#comment-13158527

Steven E. Harris commented on FELIX-2950:

The work introduces type parameters to type org.osgi.util.tracker.ServiceTracker, but the
latest available OSGi Compendium Jar file I can find is stuck at version 4.2. In a project
that has both the Felix "main" Jar file and the Compendium Jar file on the same class path
(in the host application, not just bundles looking to import ServiceTracker from some other
bundle), the two variants of ServiceTracker can't be reconciled.

Is there a newer Compendium Jar file available that includes the generics-augmented types?
I was expecting to find an updated Compendium Jar file to match the OSGi Core Jar file at
version 4.3.
> [Framework] Adopt OSGi R4.3 API as framework internal API
> ---------------------------------------------------------
>                 Key: FELIX-2950
>                 URL: https://issues.apache.org/jira/browse/FELIX-2950
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework, Specification compliance
>    Affects Versions: framework-3.2.2
>            Reporter: Richard S. Hall
>            Assignee: Richard S. Hall
>             Fix For: framework-4.0.0
> The R4.3 specification introduces more detailed API modeling bundle revisions and wiring.
Rather than just facading our existing abstractions for these concepts, we should modify the
framework implementation to adopt them wholesale (i.e., replace our existing abstractions
with the spec'ed abstractions). Although the standard abstractions do not map one-to-one with
our existing abstractions, they are reasonably close and the benefit of having an implementation
that is consistent with the standard API probably outweighs the cost of changing, since very
few people actually depend on our internal API.
> This issue will only be used for this internal refactoring process and generally will
not be used as the issue for implementing new R4.3 functionality. We'll try to introduce separate
issues for new any new functionality to make the change log more meaningful.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message