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 ax...@ws.apache.org on 2004/10/08 11:27:51 UTC

[jira] Closed: (AXISCPP-168) SOAP Fault messages not being properly deserialized

Message:

   The following issue has been closed.

   Resolver: Fred Preston
       Date: Fri, 8 Oct 2004 2:26 AM

The problem for which this defect was raised is now closed.  There is however a broader issue with exceptions.
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXISCPP-168

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXISCPP-168
    Summary: SOAP Fault messages not being properly deserialized
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Axis-C++
 Components: 
             Serialization/Deserialization

   Assignee: Fred Preston
   Reporter: Fred Preston

    Created: Thu, 23 Sep 2004 4:33 AM
    Updated: Fri, 8 Oct 2004 2:26 AM
Environment: n/a

Description:
Problem
SOAP Fault messages not being properly deserialized

Solution
SoapDeserialiser.cpp looks for the four optional elements that may be part of the fault, these are faultcode, faultstring, faultactor and faultdetail.  Unfortunately, the SOAP spec has defined the fault detail name as just detail (why?).  Thus the deserializer was looking for the wrong name.


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