You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2018/01/19 10:29:02 UTC
[jira] [Assigned] (ARIES-1738) BeanProcessor are not removed when a
namespace is restarted
[ https://issues.apache.org/jira/browse/ARIES-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet reassigned ARIES-1738:
--------------------------------------
Assignee: Guillaume Nodet
> BeanProcessor are not removed when a namespace is restarted
> -----------------------------------------------------------
>
> Key: ARIES-1738
> URL: https://issues.apache.org/jira/browse/ARIES-1738
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
> Reporter: J. Brébec
> Assignee: Guillaume Nodet
> Priority: Major
>
> a bundle X which register a custom NamespaceHandler. This handler add into the context a BeanProcessor with a reference on an osgi service.The Bundle Y use this namespace.
> When I restart X, the bundle Y restarts, but fails with the error "The Blueprint container is being or has been destroyed"
> When a namespace is restarted, the bundle Y keeps the same instance of BlueprintContainer. However, his "processors" properties is not resetted : it owns two instances of my BeanProcessor : the first one (before the restart), and the second one (after the restart). The first instance fails because the reference is not valid anymore.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)