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 2009/06/10 14:04:07 UTC
[jira] Created: (FELIX-1213) service.ranking property not respected
for singular statically bound service reference
service.ranking property not respected for singular statically bound service reference
--------------------------------------------------------------------------------------
Key: FELIX-1213
URL: https://issues.apache.org/jira/browse/FELIX-1213
Project: Felix
Issue Type: Bug
Components: Declarative Services (SCR)
Affects Versions: scr-1.0.8
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: scr-1.0.10
Consider a component has a service reference with cardinality=0..1 (or 1..1) and policy=static. In this case only one single instance is bound to the component which is the one with the higher service ranking according to the service.ranking property and the service id as laid out in section 112.3.2, Reference Cardinality, of the OSGi Compendium Specification.
This is essentially the same bug as FELIX-950 but for statically bound services this time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1213) service.ranking property not respected
for singular statically bound service reference
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed FELIX-1213.
------------------------------------
Resolution: Invalid
Fix Version/s: (was: scr-1.0.10)
As indicated close as invalid and remove from release schedule
> service.ranking property not respected for singular statically bound service reference
> --------------------------------------------------------------------------------------
>
> Key: FELIX-1213
> URL: https://issues.apache.org/jira/browse/FELIX-1213
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Affects Versions: scr-1.0.8
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
>
> Consider a component has a service reference with cardinality=0..1 (or 1..1) and policy=static. In this case only one single instance is bound to the component which is the one with the higher service ranking according to the service.ranking property and the service id as laid out in section 112.3.2, Reference Cardinality, of the OSGi Compendium Specification.
> This is essentially the same bug as FELIX-950 but for statically bound services this time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-1213) service.ranking property not
respected for singular statically bound service reference
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved FELIX-1213.
--------------------------------------
Resolution: Fixed
Applied the same fix as for static references as FELIX-950 did for dynamic references in Rev. 783311.
> service.ranking property not respected for singular statically bound service reference
> --------------------------------------------------------------------------------------
>
> Key: FELIX-1213
> URL: https://issues.apache.org/jira/browse/FELIX-1213
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Affects Versions: scr-1.0.8
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: scr-1.0.10
>
>
> Consider a component has a service reference with cardinality=0..1 (or 1..1) and policy=static. In this case only one single instance is bound to the component which is the one with the higher service ranking according to the service.ranking property and the service id as laid out in section 112.3.2, Reference Cardinality, of the OSGi Compendium Specification.
> This is essentially the same bug as FELIX-950 but for statically bound services this time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (FELIX-1213) service.ranking property not
respected for singular statically bound service reference
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger reopened FELIX-1213:
--------------------------------------
Reopenig this issue to mark it as invalid as per the resolution of FELIX-1414.
By marking it invalid this issue is also removed from the release schedule since the functionality has not been released yet.
> service.ranking property not respected for singular statically bound service reference
> --------------------------------------------------------------------------------------
>
> Key: FELIX-1213
> URL: https://issues.apache.org/jira/browse/FELIX-1213
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Affects Versions: scr-1.0.8
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
>
> Consider a component has a service reference with cardinality=0..1 (or 1..1) and policy=static. In this case only one single instance is bound to the component which is the one with the higher service ranking according to the service.ranking property and the service id as laid out in section 112.3.2, Reference Cardinality, of the OSGi Compendium Specification.
> This is essentially the same bug as FELIX-950 but for statically bound services this time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.