Re: SEDA with Apache Camel

["Lukasz L." <Lu...@sabre.com>]

Do you mean that SEDA works with InOut? 
The SEDA consumer removes exchange from the BlockingQueue and its callback
does nothing so how it can return response?
Can you give some example usage of SEDA with InOut?


James.Strachan wrote:
> 
>> And what will
>> the Camel thread actually do? Will it block until it gets the callback
>> from
>> the seda-thread, or will it continue to put exchanges in the seda's
>> blockingqueue and then starts doing all the things after the
>> seda-component
>> when it gets a callback?
> 
> It depends on the Message Exchange Pattern (to use WSDL terminology).
> 
> http://activemq.apache.org/camel/maven/camel-core/apidocs/org/apache/camel/Exchange.html#setPattern(org.apache.camel.ExchangePattern)
> http://activemq.apache.org/camel/maven/camel-core/apidocs/org/apache/camel/ExchangePattern.html
> 
> an endpoint typically attaches the message exchange pattern - be it
> InOnly (a one way message) or InOut etc.
> 
> So if a message exchange is InOnly, the default with SEDA BTW - then
> it will be a fire and forget. The sending thread will block until its
> added to the other SEDA queue, then carry on processing the next
> message.
> 
> However if you explicitly send an InOut message exchange, the sender
> will block until it receives a response.
> 

-- 
View this message in context: http://www.nabble.com/SEDA-with-Apache-Camel-tp19107574s22882p19761043.html
Sent from the Camel - Users mailing list archive at Nabble.com.