Thanks for the explanation.
I remember, using persistent messaging was the reason to use activemq.
Christian
Another advantage of NMR is that you can easily create camel routes
unit test without OSGI container (more info here
camel.apache.org/nmr.html)
On Wed, Oct 12, 2011 at 11:08 AM, Charles Moulliard
wrote:
> NMR is an in memory bus that you can use to send sync/async objects
> without the cost of th
NMR is an in memory bus that you can use to send sync/async objects
without the cost of the serialization. Endpoints (producers/consumers)
are registered in the bus when Camel routes are started and are
available for all the bundles ! Thread pools can be configured.
NMR is not persistent compare t
Avoiding serialization is the most important one I think.
On Wed, Oct 12, 2011 at 10:01, Christian Müller wrote:
> We use the camel jms/activemq component for this.
>
> @Charles: Could you please share the advantges of camel nmr over camel
> jms/activemq with us!?
>
> Best,
> Christian
>
> On We
We use the camel jms/activemq component for this.
@Charles: Could you please share the advantges of camel nmr over camel
jms/activemq with us!?
Best,
Christian
On Wed, Oct 12, 2011 at 8:36 AM, Charles Moulliard wrote:
> Hi,
>
> On Karaf/Servicemix, the recommended approach to communicate betwee
Hi,
On Karaf/Servicemix, the recommended approach to communicate between
camel routes deployed in separate bundles is to use camel-nmr
component
Regards,
Charles
On Fri, Sep 23, 2011 at 12:40 PM, Christian Schneider
wrote:
> Hi Andrei,
>
> how about using simple OSGi services? You can creat
-
From: Christian Schneider [mailto:ch...@die-schneider.net]
Sent: 23 September 2011 12:41
To: users@camel.apache.org
Subject: Re: Best practices to communicate between Camel Contexts in different
OSGi bundles
Hi Andrei,
how about using simple OSGi services? You can create a service reference in
Hi Andrei,
how about using simple OSGi services? You can create a service reference
in your spring context and call it as a bean in a camel route.
This has the advantage that the communication is not tied to camel. So
the bundle implementing the service does not have to know about camel.
Chr
JBI & NMR uses the WSDL routing semantics and mandates XML
payloads, that is not always desired.
Regards,
Andrei.
-Original Message-
From: Freeman Fang [mailto:freeman.f...@gmail.com]
Sent: 23 September 2011 09:56
To: users@camel.apache.org
Subject: Re: Best practices to communicate
sers@camel.apache.org
Subject: Re: Best practices to communicate between Camel Contexts in different
OSGi bundles
Hi,
Another solution is use camel-nmr(camel nmr component is from Apache
Servicemix) endpoint, you may need take a look at[1] to get more details.
[1]http://camel.apache.org/nmr.html
Freema
Hi,
Another solution is use camel-nmr(camel nmr component is from Apache
Servicemix) endpoint, you may need take a look at[1] to get more
details.
[1]http://camel.apache.org/nmr.html
Freeman
On 2011-9-23, at 下午3:46, Andrei Shakirin wrote:
Hi,
I would like to ask what is the best practice
11 matches
Mail list logo
