You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Jeremy Hughes (Updated) (JIRA)" <ji...@apache.org> on 2011/10/26 18:29:32 UTC

[jira] [Updated] (ARIES-694) Proxy manager can return a stale proxy built against a previous classloader for bundles having undergone refresh

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

Jeremy Hughes updated ARIES-694:
--------------------------------

    Fix Version/s: proxy.impl-0.4
                   proxy uber bundle 0.4
    
> Proxy manager can return a stale proxy built against a previous classloader for bundles having undergone refresh
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-694
>                 URL: https://issues.apache.org/jira/browse/ARIES-694
>             Project: Aries
>          Issue Type: Bug
>            Reporter: Valentin Mahrwald
>            Assignee: Valentin Mahrwald
>             Fix For: proxy uber bundle 0.4, proxy.impl-0.4
>
>
> This scenario occurred when using a Blueprint bundle A having a service reference on a service in another bundle B, the service api is also provided by B.
> B got updated to B'. In this process A gets refreshed to use the new classes from B'. However, when Blueprint creates the service reference proxy it gets returned a proxy implementing the old interfaces from B rather than the interfaces passed in (which come from B'). This is because proxy classes are cached by bundle and the bundle has not changed ....

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira