You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2008/08/02 20:55:44 UTC
[jira] Created: (SYNAPSE-418) JMSSender#processSyncResponse
incorrectly sets serverSide to true
JMSSender#processSyncResponse incorrectly sets serverSide to true
-----------------------------------------------------------------
Key: SYNAPSE-418
URL: https://issues.apache.org/jira/browse/SYNAPSE-418
Project: Synapse
Issue Type: Bug
Affects Versions: NIGHTLY
Environment: N/A
Reporter: Andreas Veithen
Assignee: Asankha C. Perera
JMSSender#processSyncResponse always calls MessageContext#setServerSide(true). This causes a failure in one of the recently added JMS unit test that uses code similar to ServiceClient#sendReceive. Indeed, if serverSide is true, AxisEngine.receive will try to invoke a MessageReceiver which doesn't exist in this case.
Since the meaning of the serverSide property is not entirely clear (see also AXIS2-2096), I'm not sure about the correct solution for this issue.
Asankha, can you have a look at this?
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-418) JMSSender#processSyncResponse
incorrectly sets serverSide to true
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758955#action_12758955 ]
Ruwan Linton commented on SYNAPSE-418:
--------------------------------------
Folks, this is fixed on the synapse trunk as well as on the 1.3 branch and will be available with the synapse-1.3 release.
Ruwan
> JMSSender#processSyncResponse incorrectly sets serverSide to true
> -----------------------------------------------------------------
>
> Key: SYNAPSE-418
> URL: https://issues.apache.org/jira/browse/SYNAPSE-418
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: NIGHTLY
> Environment: N/A
> Reporter: Andreas Veithen
> Assignee: Ruwan Linton
> Fix For: 1.3
>
>
> JMSSender#processSyncResponse always calls MessageContext#setServerSide(true). This causes a failure in one of the recently added JMS unit test that uses code similar to ServiceClient#sendReceive. Indeed, if serverSide is true, AxisEngine.receive will try to invoke a MessageReceiver which doesn't exist in this case.
> Since the meaning of the serverSide property is not entirely clear (see also AXIS2-2096), I'm not sure about the correct solution for this issue.
> Asankha, can you have a look at this?
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-418) JMSSender#processSyncResponse
incorrectly sets serverSide to true
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741405#action_12741405 ]
Ruwan Linton commented on SYNAPSE-418:
--------------------------------------
Can you specifically say what sort of an issue that you are facing with implementing the pipeline pattern?
> JMSSender#processSyncResponse incorrectly sets serverSide to true
> -----------------------------------------------------------------
>
> Key: SYNAPSE-418
> URL: https://issues.apache.org/jira/browse/SYNAPSE-418
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: NIGHTLY
> Environment: N/A
> Reporter: Andreas Veithen
> Assignee: Asankha C. Perera
>
> JMSSender#processSyncResponse always calls MessageContext#setServerSide(true). This causes a failure in one of the recently added JMS unit test that uses code similar to ServiceClient#sendReceive. Indeed, if serverSide is true, AxisEngine.receive will try to invoke a MessageReceiver which doesn't exist in this case.
> Since the meaning of the serverSide property is not entirely clear (see also AXIS2-2096), I'm not sure about the correct solution for this issue.
> Asankha, can you have a look at this?
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-418) JMSSender#processSyncResponse
incorrectly sets serverSide to true
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630322#action_12630322 ]
Andreas Veithen commented on SYNAPSE-418:
-----------------------------------------
Two additional comments:
* The issue has been confirmed here: http://www.nabble.com/Adding-Smtp-and-jms-transports-to-transport-module-to19368579.html#a19368579
* The HTTP transport seems to be affected by the same problem.
> JMSSender#processSyncResponse incorrectly sets serverSide to true
> -----------------------------------------------------------------
>
> Key: SYNAPSE-418
> URL: https://issues.apache.org/jira/browse/SYNAPSE-418
> Project: Synapse
> Issue Type: Bug
> Affects Versions: NIGHTLY
> Environment: N/A
> Reporter: Andreas Veithen
> Assignee: Asankha C. Perera
>
> JMSSender#processSyncResponse always calls MessageContext#setServerSide(true). This causes a failure in one of the recently added JMS unit test that uses code similar to ServiceClient#sendReceive. Indeed, if serverSide is true, AxisEngine.receive will try to invoke a MessageReceiver which doesn't exist in this case.
> Since the meaning of the serverSide property is not entirely clear (see also AXIS2-2096), I'm not sure about the correct solution for this issue.
> Asankha, can you have a look at this?
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-418) JMSSender#processSyncResponse
incorrectly sets serverSide to true
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen updated SYNAPSE-418:
------------------------------------
Component/s: Transports
> JMSSender#processSyncResponse incorrectly sets serverSide to true
> -----------------------------------------------------------------
>
> Key: SYNAPSE-418
> URL: https://issues.apache.org/jira/browse/SYNAPSE-418
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: NIGHTLY
> Environment: N/A
> Reporter: Andreas Veithen
> Assignee: Asankha C. Perera
>
> JMSSender#processSyncResponse always calls MessageContext#setServerSide(true). This causes a failure in one of the recently added JMS unit test that uses code similar to ServiceClient#sendReceive. Indeed, if serverSide is true, AxisEngine.receive will try to invoke a MessageReceiver which doesn't exist in this case.
> Since the meaning of the serverSide property is not entirely clear (see also AXIS2-2096), I'm not sure about the correct solution for this issue.
> Asankha, can you have a look at this?
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-418) JMSSender#processSyncResponse
incorrectly sets serverSide to true
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741438#action_12741438 ]
Andreas Veithen commented on SYNAPSE-418:
-----------------------------------------
There is more information in WSCOMMONS-444. A workaround is to reverse patch the change in r748972 and to build WS-Commons Transports with that.
> JMSSender#processSyncResponse incorrectly sets serverSide to true
> -----------------------------------------------------------------
>
> Key: SYNAPSE-418
> URL: https://issues.apache.org/jira/browse/SYNAPSE-418
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: NIGHTLY
> Environment: N/A
> Reporter: Andreas Veithen
> Assignee: Asankha C. Perera
>
> JMSSender#processSyncResponse always calls MessageContext#setServerSide(true). This causes a failure in one of the recently added JMS unit test that uses code similar to ServiceClient#sendReceive. Indeed, if serverSide is true, AxisEngine.receive will try to invoke a MessageReceiver which doesn't exist in this case.
> Since the meaning of the serverSide property is not entirely clear (see also AXIS2-2096), I'm not sure about the correct solution for this issue.
> Asankha, can you have a look at this?
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Resolved: (SYNAPSE-418) JMSSender#processSyncResponse
incorrectly sets serverSide to true
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruwan Linton resolved SYNAPSE-418.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.3
Fixed for the 1.3 release
> JMSSender#processSyncResponse incorrectly sets serverSide to true
> -----------------------------------------------------------------
>
> Key: SYNAPSE-418
> URL: https://issues.apache.org/jira/browse/SYNAPSE-418
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: NIGHTLY
> Environment: N/A
> Reporter: Andreas Veithen
> Assignee: Ruwan Linton
> Fix For: 1.3
>
>
> JMSSender#processSyncResponse always calls MessageContext#setServerSide(true). This causes a failure in one of the recently added JMS unit test that uses code similar to ServiceClient#sendReceive. Indeed, if serverSide is true, AxisEngine.receive will try to invoke a MessageReceiver which doesn't exist in this case.
> Since the meaning of the serverSide property is not entirely clear (see also AXIS2-2096), I'm not sure about the correct solution for this issue.
> Asankha, can you have a look at this?
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Assigned: (SYNAPSE-418) JMSSender#processSyncResponse
incorrectly sets serverSide to true
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruwan Linton reassigned SYNAPSE-418:
------------------------------------
Assignee: Ruwan Linton (was: Asankha C. Perera)
> JMSSender#processSyncResponse incorrectly sets serverSide to true
> -----------------------------------------------------------------
>
> Key: SYNAPSE-418
> URL: https://issues.apache.org/jira/browse/SYNAPSE-418
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: NIGHTLY
> Environment: N/A
> Reporter: Andreas Veithen
> Assignee: Ruwan Linton
>
> JMSSender#processSyncResponse always calls MessageContext#setServerSide(true). This causes a failure in one of the recently added JMS unit test that uses code similar to ServiceClient#sendReceive. Indeed, if serverSide is true, AxisEngine.receive will try to invoke a MessageReceiver which doesn't exist in this case.
> Since the meaning of the serverSide property is not entirely clear (see also AXIS2-2096), I'm not sure about the correct solution for this issue.
> Asankha, can you have a look at this?
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-418) JMSSender#processSyncResponse
incorrectly sets serverSide to true
Posted by "Chuck Swanberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741343#action_12741343 ]
Chuck Swanberg commented on SYNAPSE-418:
----------------------------------------
Is there a workaround for this? Maybe I'm wrong, but it seems to prevent me from implementing the eip pipeline pattern in synapse... Thanks...
> JMSSender#processSyncResponse incorrectly sets serverSide to true
> -----------------------------------------------------------------
>
> Key: SYNAPSE-418
> URL: https://issues.apache.org/jira/browse/SYNAPSE-418
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: NIGHTLY
> Environment: N/A
> Reporter: Andreas Veithen
> Assignee: Asankha C. Perera
>
> JMSSender#processSyncResponse always calls MessageContext#setServerSide(true). This causes a failure in one of the recently added JMS unit test that uses code similar to ServiceClient#sendReceive. Indeed, if serverSide is true, AxisEngine.receive will try to invoke a MessageReceiver which doesn't exist in this case.
> Since the meaning of the serverSide property is not entirely clear (see also AXIS2-2096), I'm not sure about the correct solution for this issue.
> Asankha, can you have a look at this?
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org