axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fred Preston (JIRA)" <axis-c-...@ws.apache.org>
Subject [jira] Commented: (AXISCPP-472) SoapSerializer::setOutputStream does not throw an exception when a problem in serialisation occurs
Date Mon, 21 Mar 2005 18:41:21 GMT
     [ http://issues.apache.org/jira/browse/AXISCPP-472?page=comments#action_61344 ]
     
Fred Preston commented on AXISCPP-472:
--------------------------------------

The serialiser code has many calls to other methods, some of which return either AXIS_FAIL
or AXIS_SUCCESS.  Whilst debugging, I noticed that some of the methods where either not checking
the return value and/or not returning an AXIS_FAIL when the serialiser had failed to serialise
an object correctly.  This could lead to dead-locks because the AxisClient may be waiting
for a response to a message that was never transmitted.

> 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
>     Assignee: 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


Mime
View raw message