[jira] Commented: (SANDESHA2C-68) Transport sender gets replaced by sandesha2 transport sender

    [ https://issues.apache.org/jira/browse/SANDESHA2C-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645179#action_12645179 ] 

Damitha Kumarage commented on SANDESHA2C-68:
--------------------------------------------

There is nothing wrong with this. This technique is used  to pass the message context through the rest of the phases/handlers before storing the message context in the storage. However there should be a real transport sender invoke after this. If it does not happen with your case then it is a problem.

> Transport sender gets replaced by sandesha2 transport sender
> ------------------------------------------------------------
>
>                 Key: SANDESHA2C-68
>                 URL: https://issues.apache.org/jira/browse/SANDESHA2C-68
>             Project: Sandesha2/C
>          Issue Type: Bug
>            Reporter: Danushka Menikkumbura
>
> In dual-channel case the transport sender in message context gets replaced by the sandesha2 transport sender on client side.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.