OK - understood in which case both Christian and Charles' suggestions are best - look at http://camel.apache.org/direct.html - for the a good example of chaining routes together and SEDA - http://camel.apache.org/seda.html
thanks, Rob On 28 May 2013, at 09:33, Mohammad Shadab Ali <mohammad.a...@genpact.com> wrote: > Hi Robert, > > With two different processes I mean two different camel routes. > > Regards, > Shadab > > -----Original Message----- > From: Robert Davies [mailto:rajdav...@gmail.com] > Sent: Monday, May 27, 2013 10:28 PM > To: users@camel.apache.org > Subject: Re: Communication between two processes without using external > messaging systems or files > > I was assuming Shadab meant different operating system processes ? > On 27 May 2013, at 17:53, Christian Müller <christian.muel...@gmail.com> > wrote: > >> Have a look at the direct und the seda Camel component. >> >> Best, >> Christian >> >> Sent from a mobile device >> Am 27.05.2013 11:56 schrieb "Mohammad Shadab Ali" >> <mohammad.a...@genpact.com >>> : >> >>> 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. >>> >>> > > > *** 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. >
