Hi,
You cannot do it the way you have detailed. The endpoint in the from()
clause will create a TCP Listener and bind to a socket (aka server).
You could do the following and accomplish your objective
In Client
----------
from (...)
.to(mina:tcp://localhost:5000?sync=true") // Client
.to("bean:processResponse");
In Server
----------
from(mina:tcp://localhost:5000?sync=true") // Server
.to("bean:processData");
Hope this helps.
Cheers,
Ashwin...
Muhammad Ichsan wrote:
>
> Dear All,
>
> I tried to use mina endpoints. I see that mina endpoints which is used
> in <from> will act as servers and the ones which is used in <to> will
> act as clients.
>
> Actually, I need mina endpoints which more or less defined as the
> following code:
>
> <from uri="mina:tcp://localhost?as_server=false"><!-- act as client .
> This endpoint connects to a server -->
> <to uri="processData">
> <to uri="mina:tcp://localhost?as_server=false"><!-- return the result
> using THE SAME socket -->
>
> Is it possible?
>
> Thanks!
>
> --
> ~The best men are men who benefit to others
> http://michsan.web.id
>
> Yang berkualitas memang beda rasanya!
> http://rizqi-cookies.com
>
>
-----
---
Ashwin Karpe, Principal Consultant, PS - Opensource Center of Competence
Progress Software Corporation
14 Oak Park Drive
Bedford, MA 01730
---
+1-972-304-9084 (Office)
+1-972-971-1700 (Mobile)
----
Blog: http://opensourceknowledge.blogspot.com/
--
View this message in context:
http://old.nabble.com/Mina-endpoint-behaviour-tp28104796p28107778.html
Sent from the Camel - Users mailing list archive at Nabble.com.
