Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
NIGHTLY
-
None
-
N/A
Description
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?
Attachments
Issue Links
- depends upon
-
WSCOMMONS-444 AbstractTransportSender should mark a synchronous reply as 'serverSide'
- Resolved