[
https://issues.apache.org/jira/browse/ARIES-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16332319#comment-16332319
]
ASF subversion and git services commented on ARIES-1738:
--------------------------------------------------------
Commit 1821662 from [~gnt] in branch 'aries/trunk'
[ https://svn.apache.org/r1821662 ]
[ARIES-1738] BeanProcessor are not removed when a namespace is restarted
> 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
> Fix For: blueprint-core-1.9.0
>
>
> 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)
