[jira] [Commented] (ARIES-1233) Stale service reference retention on consumer bundle after service provider bundle update.

["Jamie goodyear (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARIES-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14077896#comment-14077896 ] 

Jamie goodyear commented on ARIES-1233:
---------------------------------------


Each of the Consumers contain blueprint wiring similar to below:
{code}
<bean id="bizbaz" class="fu.bar.consumer.SomeClass">
    <property name="testService" ref="serviceName" /> 
</bean>

<reference interface="fu.bar" id="serviceName" availability="mandatory">
    <reference-listener bind-method="onBind" unbind-method="onUnbind">
        <bean class="fu.bar.consumer.Listener" />
    </reference-listener>
</reference>
{code}

> Stale service reference retention on consumer bundle after service provider bundle update.
> ------------------------------------------------------------------------------------------
>
>                 Key: ARIES-1233
>                 URL: https://issues.apache.org/jira/browse/ARIES-1233
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>         Environment: Apache Karaf 3.0.1
>            Reporter: Jamie goodyear
>
> Three Bundles, A, B, and C.
> Bundle A provides a service, which is wired via BP.
> Bundles B and C consume the service via BP references. Service trackers are enabled, showing that both bundles are aware of when the service provider updates.
> Bundle A configuration property tells the service to use bundle B or C for processing. Upon a configuration update the consuming bundles B and C will contain stale references to the Bundle A service. Refreshing/Restarting their bundles will correct the wiring. The BP container should refresh these service references automatically.
> I'm working on a stripped down demonstration test case to illustrate the issue.



--
This message was sent by Atlassian JIRA
(v6.2#6252)