[
https://issues.apache.org/jira/browse/ARIES-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Mahrwald resolved ARIES-694.
-------------------------------------
Resolution: Fixed
Resolved in #1141508 and #1141523 by sanity checking the classloader used for
proxying and refreshing it if necessary.
> 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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
