Hi,
camel-jms support the Request/Reply[1] EIP out of box.
In you case, you could let use the polling thread to send the request to
the message queue and wait for the response.
If you want to correlate the request message and response message
yourself in different thread, you need to set up a map of the
correlationID and SOCKET, then your response receiving thread can know
which socket it can use to send the response to tcp/ip system.
[1]http://camel.apache.org/request-reply.html
Willem
Carlo Camerino wrote:
hi,
my usecase is somewhat like this,
i'm connecting a legacy system via tcp/ip.
I plan to multiplex that tcp/ip port by putting in a receiver thread that
continuously polls the result. requesting threads can sort of queue their
request and wait for the proper reply.
while waiting for their reply the requesting threads have to wait until they
become notified...
i don't know how could this be done yet. i can start a polling consumer from
the tcp/ip but i'm thinking of how to correlate the response messages with
the proper waiting request thread.
carlo
On Wed, Aug 5, 2009 at 2:37 PM, Claus Ibsen <claus.ib...@gmail.com> wrote:
On Tue, Aug 4, 2009 at 9:07 PM, Carlo Camerino<carlo.camer...@gmail.com>
wrote:
Hi,
Does camel implement the smart proxy integration pattern?
There is no specific DSL in Camel that implements the smart proxy.
You should be able to use the existing blocks in Camel to assemble the
smart proxy.
What is your use case?
Thanks
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus