RawXMLINOutAsyncMessageReceiver faced same issues similar to 1293, 1286
-----------------------------------------------------------------------
Key: AXIS2-1296
URL: http://issues.apache.org/jira/browse/AXIS2-1296
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Reporter: Asankha C. Perera
Assigned To: Asankha C. Perera
Priority: Minor
RawXMLINOutAsyncMessageReceiver is vulnarable to picking up a wrong method [not
of the form OMElement <<method>>(OMElement e)] as well as not returning an
empty body if the ServiceClass returns null (JIRA's AXIS2-1293, AXIS2-1286)
Note: Also both RawXMLINOutAsyncMessageReceiver and
RPCInOutAsyncMessageReceiver suffered from an OM defect as the Async MR
processes the message in a different thread - sometimes after the original
stream is not available anymore. This was fixed by Chinthaka and committed
alredy
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
