Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of rajdavies@gmail.com designates
 74.125.82.47 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Communication between two processes without using external
 messaging systems or files
From: Robert Davies <rajdavies@gmail.com>
In-Reply-To: 
 <392E7ED9F266794DA841B356A22CF5B8D673429FD1@MBXNDA.headstrong.com>
Date: Tue, 28 May 2013 10:17:30 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <AFBEFDBE-794E-4C39-AF4C-8160C5D033A7@gmail.com>
References: <392E7ED9F266794DA841B356A22CF5B8D6733795CD@MBXNDA.headstrong.com>
 <CALvzYd_D_u1y=eKkH7FoPMSO_FPteRppmb78mbNoSnttzXS2eg@mail.gmail.com>
 <0EE829AA-ACBD-479C-B802-9B38D44F6E03@gmail.com>
 <392E7ED9F266794DA841B356A22CF5B8D673429FD1@MBXNDA.headstrong.com>
To: users@camel.apache.org

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.Ali5@genpact.com> wrote:

> Hi Robert,
>=20
> With two different processes I mean two different camel routes.
>=20
> Regards,
> Shadab
>=20
> -----Original Message-----
> From: Robert Davies [mailto:rajdavies@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
>=20
> I was assuming Shadab meant different operating system  processes ?
> On 27 May 2013, at 17:53, Christian M=FCller =
<christian.mueller@gmail.com> wrote:
>=20
>> Have a look at the direct und the seda Camel component.
>>=20
>> Best,
>> Christian
>>=20
>> Sent from a mobile device
>> Am 27.05.2013 11:56 schrieb "Mohammad Shadab Ali"
>> <Mohammad.Ali5@genpact.com
>>> :
>>=20
>>> Hi,
>>>=20
>>> 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.
>>>=20
>>> Regards,
>>> Shadab
>>>=20
>>> ________________________________
>>> *** 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.***
>>>=20
>>> 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.
>>>=20
>>>=20
>=20
>=20
> *** 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=20
> contents or any action taken in reliance on it is unlawful. Unintended =
recipients must notify the sender immediately=20
> by e-mail/phone & delete it from their system without making any =
copies or disclosing it to a third person.
>=20