[
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
