On Wed, Jun 20, 2012 at 10:21 PM, Alexander Kaiser
wrote:
> Hi Claus,
>
> thanks for your reply! The protocol is indeed line based. I actually tried
> to write my own codec, but without success, the decode method always was
> called two times, and only the result of the first call ended up in the
Hi Claus,
thanks for your reply! The protocol is indeed line based. I actually tried
to write my own codec, but without success, the decode method always was
called two times, and only the result of the first call ended up in the
message body. That's why I was asking for mina2 docu.
Anyway, I end
On Mon, Jun 18, 2012 at 3:05 PM, Alexander Kaiser
wrote:
> Hi,
>
> I am trying to connect to a server with mina. The server sends a hello
> message on socket connect, then I send it a command and want to receive the
> servers reply in the message body.
>
> camel-mina connects server
>
If you cant wait for the new mina component you will have to write your own
camel component to do this - at least that is what I ended up doing!
Im new to camel so what I did cannot have the best implementation strategy,
so I will probably replace with the mentioned mina2 component. However a
brief
You will only get one reply if you're using the camel-mina component. The
camel-mina2 component will handle multiple replies. It is not complete yet.
Regards,
Chad
Sent from my iPhone
On Jan 18, 2012, at 3:39 PM, mgiammarco wrote:
> I have the same problem. I send a message and I expect sev
I have the same problem. I send a message and I expect several ASYNC replies.
Unfortunately I get only ONE reply using either an activemq client with
camel and a java stomp client.
--
View this message in context:
http://camel.465427.n5.nabble.com/Single-request-with-multiple-replies-over-TCP-tp5
Thanks Ioannis however the 'responses' are never ending. Which is why I
mentioned its like pub/sub.
The two applications I have use an 'always open' TCP connection where the in
and out messages streams are effectively 'sessionless'. E.g.
TCP Client opens connection with TCP Sever Listener .
Clien
If you are expecting one message for each response, then I guess that you
can get this message back by having the sync option set to true.
However, I think that you mentioned multiple responses per request. I think
that you could easily solve this one by implementing the appropriate
filter, that wo
