[
https://issues.apache.org/activemq/browse/CAMEL-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54807#action_54807
]
Barry Kaplan commented on CAMEL-1077:
-------------------------------------
Are there any plans to pursue this? I'm in the process of of unwinding my use
of came-mina since I need my mina-server(acceptor) to the message-producer and
my mina-client(connector) to the be message-receiver.
> tcp client mode / server mode determined by "to" or "from" elements limits
> usability.
> -------------------------------------------------------------------------------------
>
> Key: CAMEL-1077
> URL: https://issues.apache.org/activemq/browse/CAMEL-1077
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-mina
> Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0
> Reporter: Jeff Vienneau
>
> Internally,
> MinaProducer is coded to create a Mina connector (client mode socket).
> MinaConsumer is coded to create a Mina acceptor (server mode socket).
> Additionally, it appears a producer (client mode socket) is created for a
> "to" route mapping and a consumer (server mode socket) is created for a
> "from" route mapping.
> This means an endpoint cannot be created in which the session is initiated by
> a client and messages are routed "to" the client.
> The opposite is also true, an endpoint with a "from" route mapping cannot
> establish a connection to a tcp server.
> This is a major limitation, as we do not often have control over the systems
> with which we are interfacing.
> Perhaps, the mina::tcp URI could have a parameter the sets the socket mode:
> tcp.mode=server or tcp.mode=client.
> Hope this make sense, thanks!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
