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 2012/09/24 10:15:07 UTC

[jira] [Resolved] (FELIX-3679) Component names need not be globally unique any more

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

Felix Meschberger resolved FELIX-3679.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: scr-1.6.2

Fixed in Rev. 1389240 and tested against the OSGi CT.
                
> Component names need not be globally unique any more
> ----------------------------------------------------
>
>                 Key: FELIX-3679
>                 URL: https://issues.apache.org/jira/browse/FELIX-3679
>             Project: Felix
>          Issue Type: Task
>          Components: Declarative Services (SCR), Specification compliance
>    Affects Versions:  scr-1.6.0
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: scr-1.6.2
>
>
> DS 1.1 introduced an unnoticed change in the specification of the component name: While DS 1.0 required the component name to be globally unique this has been relaxed in DS 1.1 where the component name must "only" be unique within the bundle.
> Our implementation still forces component names to always be unique. We should differentiate between 1.0 and 1.1+ components: names of 1.0 components must be globally unique while 1.1 (and later) components must be unique within the bundle.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira