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 2019/08/06 05:22:00 UTC

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

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

Claus Ibsen resolved CAMEL-7970.
--------------------------------
       Resolution: Fixed
         Assignee: Claus Ibsen
    Fix Version/s: 3.0.0.M5

There is a destroy method on camel context tracker now

> Container does not see the unregister event
> -------------------------------------------
>
>                 Key: CAMEL-7970
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7970
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.14.0
>            Reporter: Thomas Diesler
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 3.0.0, 3.0.0.M5
>
>
> 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
(v7.6.14#76016)