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 "John Hawkins (JIRA)" <ax...@ws.apache.org> on 2005/02/01 11:48:23 UTC
[jira] Commented: (AXISCPP-194) Inconsistant deserialization error reporting in generated code.
[ http://issues.apache.org/jira/browse/AXISCPP-194?page=comments#action_58373 ]
John Hawkins commented on AXISCPP-194:
--------------------------------------
Is this still a problem?
> 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/Deserialization
> Versions: 1.3 Beta
> Environment: All platforms
> Reporter: Samisa Abeysinghe
> Priority: Minor
>
> 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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira