[ 
https://issues.apache.org/jira/browse/AXIS2-4944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116242#comment-13116242
 ] 

Paul Hodchenkov commented on AXIS2-4944:
----------------------------------------

I have found four use cases which should be supported when using local 
transport in ESB:
1) proxy->proxy (works fine with NonBlockingLocalTransportSender)
2) proxy->service (works fine with NonBlockingLocalTransportSender)
3) proxy->mediator blocking call-> service  (works fine with 
LocalTransportSender)
4) proxy->mediator blocking call->proxy->proxy (LocalTransportSender and 
NonBlockingLocalTransportSender can't handle this scenario)
                
> Improve Axis2 local transport to work with Apache Synapse's nhttp transport 
> ----------------------------------------------------------------------------
>
>                 Key: AXIS2-4944
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4944
>             Project: Axis2
>          Issue Type: Improvement
>          Components: transports
>    Affects Versions: nightly
>         Environment: Ubuntu 10.04
> Sun JDK 1.6
>            Reporter: Heshan Suriyaarachchi
>            Assignee: Ruwan Linton
>             Fix For: 1.7.0
>
>         Attachments: AXIS2-4944-patch-ver2.txt, AXIS2-4944-patch-ver3.txt, 
> AXIS2-4944-patch-ver5.txt, AXIS2-4944-patch.txt, synapse.xml
>
>
> Currently we can not use the axis2 local-transport with Apache Synapse's 
> nhttp transport.  
> I am looking into improving the existing local-transport of axis2 to work 
> with nhttp transport. 
> I will provide a patch to fix this. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to