axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From axis-c-...@ws.apache.org
Subject [jira] Updated: (AXISCPP-194) Inconsistant deserialization error reporting in generated code.
Date Fri, 15 Oct 2004 11:10:52 GMT
The following issue has been updated:

    Updater: John Hawkins (mailto:hawkinsj@uk.ibm.com)
       Date: Fri, 15 Oct 2004 4:10 AM
    Changes:
             type changed from Bug to Improvement
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/AXISCPP-194?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXISCPP-194

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXISCPP-194
    Summary: Inconsistant deserialization error reporting in generated code.
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Axis-C++
 Components: 
             Serialization/Deserialization
   Versions:
             1.3 Beta

   Assignee: 
   Reporter: Samisa Abeysinghe

    Created: Thu, 7 Oct 2004 6:15 PM
    Updated: Fri, 15 Oct 2004 4:10 AM
Environment: All platforms

Description:
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.




---------------------------------------------------------------------
JIRA INFORMATION:
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