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 2007/09/17 11:30:32 UTC
[jira] Created: (FELIX-366) Bound Service Replacement incorrect
Bound Service Replacement incorrect
-----------------------------------
Key: FELIX-366
URL: https://issues.apache.org/jira/browse/FELIX-366
Project: Felix
Issue Type: Bug
Components: Declarative Services
Reporter: Felix Meschberger
Currently SCR implements incorrect bound service replacement for references of unary cardinality: Instead of first binding the new (replacement) service and then unbinding the old (outgoing) service, the old service is first unbound and then the replacement bound. This violates the specification in section 112.5.10, Bound Service Replacement, of the Declarative Services Specification.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-366) Bound Service Replacement incorrect
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated FELIX-366:
------------------------------------
Fix Version/s: 1.0.0
> Bound Service Replacement incorrect
> -----------------------------------
>
> Key: FELIX-366
> URL: https://issues.apache.org/jira/browse/FELIX-366
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 1.0.0
>
>
> Currently SCR implements incorrect bound service replacement for references of unary cardinality: Instead of first binding the new (replacement) service and then unbinding the old (outgoing) service, the old service is first unbound and then the replacement bound. This violates the specification in section 112.5.10, Bound Service Replacement, of the Declarative Services Specification.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (FELIX-366) Bound Service Replacement
incorrect
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on FELIX-366 started by Felix Meschberger.
> Bound Service Replacement incorrect
> -----------------------------------
>
> Key: FELIX-366
> URL: https://issues.apache.org/jira/browse/FELIX-366
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
>
> Currently SCR implements incorrect bound service replacement for references of unary cardinality: Instead of first binding the new (replacement) service and then unbinding the old (outgoing) service, the old service is first unbound and then the replacement bound. This violates the specification in section 112.5.10, Bound Service Replacement, of the Declarative Services Specification.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-366) Bound Service Replacement incorrect
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger reassigned FELIX-366:
---------------------------------------
Assignee: Felix Meschberger
> Bound Service Replacement incorrect
> -----------------------------------
>
> Key: FELIX-366
> URL: https://issues.apache.org/jira/browse/FELIX-366
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
>
> Currently SCR implements incorrect bound service replacement for references of unary cardinality: Instead of first binding the new (replacement) service and then unbinding the old (outgoing) service, the old service is first unbound and then the replacement bound. This violates the specification in section 112.5.10, Bound Service Replacement, of the Declarative Services Specification.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-366) Bound Service Replacement incorrect
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated FELIX-366:
------------------------------------
Fix Version/s: (was: felix-1.0.0)
scr-1.0.0
> Bound Service Replacement incorrect
> -----------------------------------
>
> Key: FELIX-366
> URL: https://issues.apache.org/jira/browse/FELIX-366
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: scr-1.0.0
>
>
> Currently SCR implements incorrect bound service replacement for references of unary cardinality: Instead of first binding the new (replacement) service and then unbinding the old (outgoing) service, the old service is first unbound and then the replacement bound. This violates the specification in section 112.5.10, Bound Service Replacement, of the Declarative Services Specification.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-366) Bound Service Replacement incorrect
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529437 ]
Felix Meschberger commented on FELIX-366:
-----------------------------------------
Deployed new snapshot build containing this fix.
> Bound Service Replacement incorrect
> -----------------------------------
>
> Key: FELIX-366
> URL: https://issues.apache.org/jira/browse/FELIX-366
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 1.0.0
>
>
> Currently SCR implements incorrect bound service replacement for references of unary cardinality: Instead of first binding the new (replacement) service and then unbinding the old (outgoing) service, the old service is first unbound and then the replacement bound. This violates the specification in section 112.5.10, Bound Service Replacement, of the Declarative Services Specification.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-366) Bound Service Replacement incorrect
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed FELIX-366.
-----------------------------------
Resolution: Fixed
After the plugin has been updated to take care of the correct service replacement semantics, the SCR is also fixed.
Fixed in Rev. 576795
> Bound Service Replacement incorrect
> -----------------------------------
>
> Key: FELIX-366
> URL: https://issues.apache.org/jira/browse/FELIX-366
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
>
> Currently SCR implements incorrect bound service replacement for references of unary cardinality: Instead of first binding the new (replacement) service and then unbinding the old (outgoing) service, the old service is first unbound and then the replacement bound. This violates the specification in section 112.5.10, Bound Service Replacement, of the Declarative Services Specification.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (FELIX-366) Bound Service Replacement
incorrect
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on FELIX-366 started by Felix Meschberger.
> Bound Service Replacement incorrect
> -----------------------------------
>
> Key: FELIX-366
> URL: https://issues.apache.org/jira/browse/FELIX-366
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
>
> Currently SCR implements incorrect bound service replacement for references of unary cardinality: Instead of first binding the new (replacement) service and then unbinding the old (outgoing) service, the old service is first unbound and then the replacement bound. This violates the specification in section 112.5.10, Bound Service Replacement, of the Declarative Services Specification.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.