camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cmoulliard <cmoulli...@gmail.com>
Subject Re: event:// component - example ?
Date Fri, 09 May 2008 07:30:46 GMT

For general purpose eventing its probably easier to use either direct:
seda: or vm: endpoints

>> Except that the Event-driven consumer pattern normally consumes messages
>> when an event is fired instead to continuously listening for incoming
>> messages for direct or vm.

Is there a difference from thread management between event:// and direct://
or vm:// ?


James.Strachan wrote:
> 
> 2008/5/8 Gert Vanthienen <gert.vanthienen@skynet.be>:
>> Charles,
>>
>>  The only example I could find is in the unit tests.  Have a look at
>> http://svn.apache.org/repos/asf/activemq/camel/trunk/components/camel-spring/src/test/java/org/apache/camel/component/event/EventRouteTest.java
>>
>>  To me, this event:// endpoint app receives events from the CamelContext
>> itself (e.g. the  ContextRefreshEvent received first in the test) as well
>> as
>> events on messages being exchange (e.g. the CamelEvent received
>> afterwards).
>> This is just what I can learn from the unit test, but I'm sure someone
>> will
>> correct me if I'm completely missing the point here...
> 
> Yeah thats correct. Basically the event:// component allows you to
> consume Spring events.
> 
> For general purpose eventing its probably easier to use either direct:
> seda: or vm: endpoints
> -- 
> James
> -------
> http://macstrac.blogspot.com/
> 
> Open Source Integration
> http://open.iona.com
> 
> 

-- 
View this message in context: http://www.nabble.com/event%3A---component---example---tp17125438s22882p17142776.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Mime
View raw message