[
https://issues.apache.org/jira/browse/WSCOMMONS-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758558#action_12758558
]
Ruwan Linton commented on WSCOMMONS-444:
----------------------------------------
There is an issue of the way that axis2 thinks about the serverSide, well for
axis2 that thinking is correct but that may not be correct from an another
software piece which uses axis2 underneath to serve its messaging requirements.
Specially when acting as a proxy or a broker.
Any way axis2 allows this parameter to be controlled by the operation client,
fortunately. So I have fixed this from the synapse side... and is already fixed
for axis2. So we can consider this as resolved.
> AbstractTransportSender should mark a synchronous reply as 'serverSide'
> -----------------------------------------------------------------------
>
> Key: WSCOMMONS-444
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-444
> Project: WS-Commons
> Issue Type: Bug
> Components: Transport
> Reporter: Asankha C. Perera
> Assignee: Ruwan Linton
> Priority: Blocker
> Fix For: Transports 1.0
>
>
> Causes a problem with the scenario described at
> http://wso2.org/forum/thread/4746
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
