You are viewing a plain text version of this content. The canonical link for it is here.

Posted to c-dev@axis.apache.org by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org> on 2005/03/17 14:29:20 UTC

[jira] Updated: (AXISCPP-472) SoapSerializer::setOutputStream does not throw an exception when a problem in serialisation occurs

     [ http://issues.apache.org/jira/browse/AXISCPP-472?page=history ]

Samisa Abeysinghe updated AXISCPP-472:
--------------------------------------

    Component: Serialization

> SoapSerializer::setOutputStream does not throw an exception when a problem in serialisation occurs
> --------------------------------------------------------------------------------------------------
>
>          Key: AXISCPP-472
>          URL: http://issues.apache.org/jira/browse/AXISCPP-472
>      Project: Axis-C++
>         Type: Bug
>   Components: Serialization
>  Environment: n/a
>     Reporter: Fred Preston

>
> SoapSerializer::setOutputStream creates the SOAP envelope and header elements.  It parses the contents of the serialised message creating headers, attributes, etc.  If an of the methods that actually perform the serialisation fail, there this method must return an exception.  Currently, it reports the failure and no message is sent.  Also, processing continues and the response side still waits for a message that it will never recieve!  An exception must be thrown when iStatus is set to AXIS_FAIL so that message transmission halts and the calling application will be made aware of an error in the message they are trying to send.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira