camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Charles Moulliard <ch0...@gmail.com>
Subject Re: Communication between two processes without using external messaging systems or files
Date Mon, 27 May 2013 18:13:22 GMT
Shabad,

If you don't want to use a JMS broker, then you should consider to use
camel seda component (http://camel.apache.org/seda.html) which uses an
internal queue (
http://docs.oracle.com/javase/1.5.0/docs/api/java/util/concurrent/BlockingQueue.html)
for async exchange. For sync exchanges, then direct must be used (
http://camel.apache.org/direct.html)

Regards,




On Mon, May 27, 2013 at 6:57 PM, Robert Davies <rajdavies@gmail.com> wrote:

> I was assuming Shadab meant different operating system  processes ?
> On 27 May 2013, at 17:53, Christian Müller <christian.mueller@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.Ali5@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.
> >>
> >>
>
>


-- 
Charles Moulliard
Apache Committer / Sr. Enterprise Architect (RedHat)
Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message