Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Date: Tue, 28 Feb 2017 01:26:35 -0700 (MST)
From: alexey-s <alexins@mail.ru>
To: users@camel.apache.org
Message-ID: <1488270394959-5794547.post@n5.nabble.com>
In-Reply-To: <1487688349587-5794194.post@n5.nabble.com>
References: <1487688349587-5794194.post@n5.nabble.com>
Subject: Re: Stop component "direct-vm" from another OSGI camelContext
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
archived-at: Tue, 28 Feb 2017 08:26:45 -0000

I conducted a series of experiments.
Normal JUnit, without OSGI. Creates 2 Camel Context.
The first contains


The second contains not a single RouteBuilder. Create only ProducerTemplate
and send body.


JUnit shows stable performance.

Go to the Apache Karaf.
The first component can be built on anything. Spring, OSGI Blueprint, OSGI
SCR or default BundleActivator. The choice does not matter.
Here it is quite different.

Create Apache Karaf Shell command


System components "direct-vm" loses its list of registered components.
There is a cleaning list DirectVmComponent.CONSUMERS.

The implementation of the command I used OsgiDefaultCamelContext.
Then I used DefaultCamelContext.
A special role is not playing.

When working in the OSGI, DirectVmComponent component does not work as
expected in JUnit.

Maybe I still see
"Also we dont encourge end user to start and stop camel context, 
as there is a bunch of stuff you need to do this so its correct."


--
View this message in context: http://camel.465427.n5.nabble.com/Stop-component-direct-vm-from-another-OSGI-camelContext-tp5794194p5794547.html
Sent from the Camel - Users mailing list archive at Nabble.com.