[
https://issues.apache.org/activemq/browse/CAMEL-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53888#action_53888
]
Jеns Riеmschneidеɾ commented on CAMEL-1942:
-------------------------------------------
The toString() methods of the SocketAddress implementations should return
something useful. Usually something of the form "host:port" or
"ip-address:port". So that should be fine.
I don't know about others, but for us the IoSession itself wasn't the important
thing. We only need the addresses. You can do a lot of things with the
IoSession that are probably not very useful. Also, the IoSession might have
been closed at the time the header is retrieved, e.g. in asynchronous routing.
So maybe it would be better to simply offer some of the data that the IoSession
offers and not the IoSession itself.
> Allow access to IoSession via message
> -------------------------------------
>
> Key: CAMEL-1942
> URL: https://issues.apache.org/activemq/browse/CAMEL-1942
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-mina
> Affects Versions: 2.0.0
> Reporter: Jеns Riеmschneidеɾ
> Assignee: Willem Jiang
> Fix For: 2.1.0
>
> Attachments: mina.patch
>
>
> In 1.x it was possible to get access to the IoSession via the MinaExchange.
> In 2.0, MinaExchange is no more and therefore access to the IoSession is
> impossible.
> Add a MinaMessage that has an accessor to the IoSession set by the
> MinaConsumer.
> Mailing List:
> http://www.nabble.com/IoSession-data-in-Exchange-created-by-MinaConsumer-td25150794.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
