[
https://issues.apache.org/jira/browse/AXIS2C-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609208#action_12609208
]
Damitha Kumarage commented on AXIS2C-1209:
------------------------------------------
Currently listener manager is started at the service client code when it is
using send_receive_non_blocking with separate listener. Since this is done for
each request it would do no harm to move this functionality into the sender.
From the sender, according to the MEP and use separate listner option we can
start it.
Also currently when creating or starting listener manager we do not pass any
transport specific paraemter list. You would also need to change listener
manager code to allow that. We need to pass that information into the loaded
transport implementation.
+1 from me for moving listener mansger sartup functionlity into sender with the
above change.
> Current Dual-channel Implementation can never Support Certain Transports
> ------------------------------------------------------------------------
>
> Key: AXIS2C-1209
> URL: https://issues.apache.org/jira/browse/AXIS2C-1209
> Project: Axis2-C
> Issue Type: Bug
> Reporter: Danushka Menikkumbura
>
> In the current dual-channel implementation, the message receiver is started
> before the message is handed over to the transport sender. This
> implementation can not support a transport receiver that depends on certain
> piece of information that is not available until the sender invocation phase.
> For an example, in AMQP, the receiver need to know the id of the queue that
> is should listen to and the queue id is not know until the transport sender
> is invoked.
> So I think we should make the implementation such that the transport sender
> has the responsibility of starting the message receiver so that the sender
> can provide the receiver with whatever the vital information that it needs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
