Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sun, 2 Nov 2014 08:43:33 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12750738.1414411514000.393480.1414917813750@Atlassian.JIRA>
In-Reply-To: <JIRA.12750738.1414411514000@Atlassian.JIRA>
References: <JIRA.12750738.1414411514000@Atlassian.JIRA>
 <JIRA.12750738.1414411514645@arcas>
Subject: [jira] [Commented] (CAMEL-7970) Container does not see the
 unregister event
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

We can add a unmanage method to org.apache.camel.spi.Container in Camel 3.0.

> 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
>             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)