You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2014/11/02 09:42:33 UTC

[jira] [Commented] (CAMEL-7970) Container does not see the unregister event

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

Claus Ibsen commented on CAMEL-7970:
------------------------------------

Yeah unfortunately that breaks the API. You can use EventNotifer to register a callback to get notified when the context is stopping/stopped.

> Container does not see the unregister event
> -------------------------------------------
>
>                 Key: CAMEL-7970
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7970
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.14.0
>            Reporter: Thomas Diesler
>             Fix For: 3.0.0
>
>
> Clients of the Container SPI see contexts being added but not removed. In wildfly we expose every context as an msc service to allow for service dependencies on it. When a context gets unregistered we must also unregister the msc service.
> unmanage(CamelContext) should probably be exposed in the same way as manage(CamelContext)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)