You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by "Asankha C. Perera (JIRA)" <ji...@apache.org> on 2009/02/27 05:34:01 UTC
[jira] Created: (WSCOMMONS-444) AbstractTransportSender should mark
a synchronous reply as 'serverSide'
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: Asankha C. Perera
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.
[jira] Assigned: (WSCOMMONS-444) AbstractTransportSender should
mark a synchronous reply as 'serverSide'
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSCOMMONS-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruwan Linton reassigned WSCOMMONS-444:
--------------------------------------
Assignee: Ruwan Linton (was: Asankha C. Perera)
> 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.
[jira] Commented: (WSCOMMONS-444) AbstractTransportSender should
mark a synchronous reply as 'serverSide'
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSCOMMONS-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737491#action_12737491 ]
Asankha C. Perera commented on WSCOMMONS-444:
---------------------------------------------
Andreas, please feel free to pick this one up if you have any ideas that would make this work for both Synapse and Axis2..
> 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: Asankha C. Perera
> 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.
[jira] Commented: (WSCOMMONS-444) AbstractTransportSender should
mark a synchronous reply as 'serverSide'
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (WSCOMMONS-444) AbstractTransportSender should
mark a synchronous reply as 'serverSide'
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSCOMMONS-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677652#action_12677652 ]
Asankha C. Perera commented on WSCOMMONS-444:
---------------------------------------------
Thanks Andreas for pointing this out...
https://issues.apache.org/jira/browse/AXIS2-2096 is a very valid and very serious JIRA.. it has caused a lot of trouble for Synapse over the years, and I think Axis2 should clean it up soon.
Now that the transports are shared, this looks like either do we want Synapse to operate correctly or Axis2 :) ? Let me dig a bit deeper to figure out a way to get both working..
> 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: Asankha C. Perera
> 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.
[jira] Resolved: (WSCOMMONS-444) AbstractTransportSender should
mark a synchronous reply as 'serverSide'
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSCOMMONS-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asankha C. Perera resolved WSCOMMONS-444.
-----------------------------------------
Resolution: Fixed
fixed and will be available with the 1.0 release of the transports
> 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: Asankha C. Perera
> 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.
[jira] Updated: (WSCOMMONS-444) AbstractTransportSender should mark
a synchronous reply as 'serverSide'
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSCOMMONS-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen updated WSCOMMONS-444:
--------------------------------------
Priority: Blocker (was: Major)
Increased priority to blocker because depending on whether the setServerSide(true) instruction is there or not, we either break Axis2 (ServiceClient) or Synapse. We need to figure out a solution that works both for ServiceClient and for Synapse.
> 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: Asankha C. Perera
> 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.
[jira] Resolved: (WSCOMMONS-444) AbstractTransportSender should
mark a synchronous reply as 'serverSide'
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSCOMMONS-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruwan Linton resolved WSCOMMONS-444.
------------------------------------
Resolution: Fixed
Can be considered as fixed since both axis2 and synapse works with the existing behaviour of the serverSide attribute.
> 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.
[jira] Reopened: (WSCOMMONS-444) AbstractTransportSender should
mark a synchronous reply as 'serverSide'
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSCOMMONS-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen reopened WSCOMMONS-444:
---------------------------------------
This change causes a regression detected by the transport tests. What happens is that the change makes the transports unusable with ServiceClient: reception of the synchronous response fails with "Message Receiver not found for AxisOperation: {http://ws.apache.org/namespaces/axis2}anonOutInOp". See also SYNAPSE-418.
> 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: Asankha C. Perera
> 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.