Hi Chad
Thanks for sharing this with us, and if / when you get the time to
help out with the camel-mina2 component.
I have said it many times, we love contributions at ASF.
On Wed, Oct 10, 2012 at 2:32 PM, Chad Beaulac wrote:
> Somebody asked me about this so I'm sharing my response with the li
Somebody asked me about this so I'm sharing my response with the list. The
question was, how do I do this now if the functionality doesn't exist in
camel-mina2 yet.
Response:
I've been working, off and on, to get this functionality into camel-mina2.
Unfortunately, my schedule with customers ke
I'm working on this now. I have some unit tests written and working. I hope
to post a patch for review soon.
The current approach allows you to attach a Mina IoHandler to a Mina2
endpoint. The IoHandler receives "n" messages from the consumer and can send
"m" responses.
-Chad
--
View this mess
OK, thank you both.
--
View this message in context:
http://camel.465427.n5.nabble.com/Asynchronous-socket-read-write-via-camel-tp5503650p5504809.html
Sent from the Camel - Users mailing list archive at Nabble.com.
There is a person working on camel-mina2 component to enhance it to
support async req/reply with correlation.
eg what seems like what you are looking for. There is some JIRA
tickets about this.
The current behavior for req/reply over netty/mina/mina2 is a 1:1
message solution.
On Wed, Feb 22, 20
Hi，
I don't think current camel netty component supports the way that you
want.
If you are happy with other camel component, you may need to think
about use netty directly.
And using the camel context inside the netty, so you can managed the
socket yourself with the help the two In-only ro
