[
https://issues.apache.org/jira/browse/AXISCPP-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra closed AXISCPP-925.
------------------------------
Resolution: Fixed
Now the code completely supports one-way messaging. Any response data that is
returned is assumed to be a fault and thus will result in the initiation of
fault processing.
For those interested, ClientAxisEngine now makes use of the transport's
isThereResponseData() method to determine if there is non-protocol data to be
consumed. If there is, then the header and body elements are consumed (as is
done for send/receive messaging). Then ClientAxisEngine invokes new
deserializer method initiateFault() which initiates a fault using the same
logic as when an element name does not match what is expected.
Works pretty good.
Also created new unit test, OneWayOperation.
> If the called Web service is 'One-Way' Type, then an Exception occurs in the
> Client
> -----------------------------------------------------------------------------------
>
> Key: AXISCPP-925
> URL: https://issues.apache.org/jira/browse/AXISCPP-925
> Project: Axis-C++
> Issue Type: Bug
> Components: Client - Engine
> Reporter: James Jose
> Assigned To: nadir amra
> Fix For: current (nightly)
>
>
> For a 'One-Way' service(Client sends a request but no response from the
> server) client results in a C++ Exception.
> 'SameComplexTypeAndElementName' Test shows this issue.
--
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]
