hi Shadab,

it really sounds like you really should be using ActiveMQ. You can run it 
embedded - collocated with your producing process - and you don't need to use 
persistence
see here how to set it up - 
http://activemq.apache.org/how-do-i-embed-a-broker-inside-a-connection.html and 
here's an example with camel - 
http://camel.apache.org/walk-through-an-example.html

I know you don't want to use ActiveMQ - but the best way to do what you want is 
actually with ActiveMQ :)

thanks,

Rob


On 27 May 2013, at 10:01, Mohammad Shadab Ali <mohammad.a...@genpact.com> wrote:

> Hi,
> 
> We have a requirement where we are having two processes. The output of one 
> process will be the input for the second one. We do not want to use the 
> external messaging systems like active MQ etc and also we do not want to use 
> file component.
> We want something like first process will dump the message in some internal 
> queue(or something else) and the second process will be polling this queue 
> for the messages.
> Is there any component available in camel to achieve this requirement.
> Thanks in advance.
> 
> Regards,
> Shadab
> 
> ________________________________
> *** This e-mail (and any attachments), is confidential and may be privileged. 
> It may be read, copied and used only
> by intended recipients. Unauthorized access to this e-mail (or attachments) 
> and disclosure or copying of its
> contents or any action taken in reliance on it is unlawful. Unintended 
> recipients must notify the sender immediately
> by e-mail/phone & delete it from their system without making any copies or 
> disclosing it to a third person.***
> 
> This e-mail (and any attachments), is confidential and may be privileged. It 
> may be read, copied and used only
> by intended recipients. Unauthorized access to this e-mail (or attachments) 
> and disclosure or copying of its 
> contents or any action taken in reliance on it is unlawful. Unintended 
> recipients must notify the sender immediately 
> by e-mail/phone & delete it from their system without making any copies or 
> disclosing it to a third person.
> 

Reply via email to