synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <>
Subject [jira] Commented: (SYNAPSE-418) JMSSender#processSyncResponse incorrectly sets serverSide to true
Date Mon, 10 Aug 2009 17:43:14 GMT


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:
>             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:
For additional commands, e-mail:

View raw message