[FELIX-366] Bound Service Replacement incorrect

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: scr-1.0.0
• Component/s: Declarative Services (SCR)
• Assignee: Felix Meschberger
• Reporter: Felix Meschberger
• Created: 17/Sep/07 09:28
• Updated: 30/May/08 18:15
• Resolved: 18/Sep/07 09:22

Description

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.

Issue Links

• is blocked by: FELIX-367 Autogenerated unbind method may incorrectly drop service