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] Closed: (AXISCPP-194) Inconsistant deserialization error reporting in generated code.
Date Wed, 05 Apr 2006 13:05:27 GMT
     [ http://issues.apache.org/jira/browse/AXISCPP-194?page=all ]
     
Fred Preston closed AXISCPP-194:
--------------------------------


> Inconsistant deserialization error reporting in generated code.
> ---------------------------------------------------------------
>
>          Key: AXISCPP-194
>          URL: http://issues.apache.org/jira/browse/AXISCPP-194
>      Project: Axis-C++
>         Type: Improvement

>   Components: Serialization
>     Versions: 1.3 Beta
>  Environment: All platforms
>     Reporter: Samisa Abeysinghe
>     Priority: Minor
>      Fix For: 1.6 Alpha

>
> In case of deserialization errors, sometimes an exception is thrown, some other times
null is returned to user.
> See issues AXISCPP-192 and AXISCPP-193 for context.
> From mailing list: Samisa ->
> In the earlier case it check the message for 
> "getCustomerProfileSoapOutput"
> and threw a "Cannot
> deserialize excaption".
> However, in case of "mmbiOutput" it does not check the message, and 
> return
> a NULL object, instead
> of thowing a "Cannot deserialize excaption" where it really has failed 
> to
> deserialize.
> Clearly the errors shown to the user, in these two occations, for the 
> same
> error, are not
> consistant and hence it is difficult to troubleshoot.
> I guess this too is something to be fixed.

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


Mime
View raw message