Return-Path: 
 <axis-c-dev-return-2299-apmail-ws-axis-c-dev-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org
Received: (qmail 55432 invoked from network); 8 Oct 2004 09:31:55 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 8 Oct 2004 09:31:55 -0000
Received: (qmail 54936 invoked by uid 500); 8 Oct 2004 09:31:55 -0000
Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org
Received: (qmail 54846 invoked by uid 500); 8 Oct 2004 09:31:55 -0000
Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:axis-c-dev-help@ws.apache.org>
list-unsubscribe: <mailto:axis-c-dev-unsubscribe@ws.apache.org>
list-post: <mailto:axis-c-dev@ws.apache.org>
List-Id: "Apache AXIS C Developers List" <axis-c-dev.ws.apache.org>
Reply-To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Delivered-To: mailing list axis-c-dev@ws.apache.org
Received: (qmail 54832 invoked by uid 99); 8 Oct 2004 09:31:54 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=NO_REAL_NAME
X-Spam-Check-By: apache.org
Received: from [192.18.33.10] (HELO exchange.sun.com) (192.18.33.10)
  by apache.org (qpsmtpd/0.28) with SMTP; Fri, 08 Oct 2004 02:31:54 -0700
Received: (qmail 6686 invoked from network); 8 Oct 2004 09:33:51 -0000
Received: from localhost (HELO nagoya) (127.0.0.1)
  by nagoya.betaversion.org with SMTP; 8 Oct 2004 09:33:51 -0000
Message-ID: <1742883159.1097228031175.JavaMail.apache@nagoya>
Date: Fri, 8 Oct 2004 02:33:51 -0700 (PDT)
From: axis-c-dev@ws.apache.org
To: axis-c-dev@ws.apache.org
Subject: [jira] Closed: (AXISCPP-170) The fault message name for details
 should be 'detail' and not 'faultdetail'
In-Reply-To: <1541326957.1096017991907.JavaMail.apache@nagoya>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Message:

   The following issue has been closed.

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

The code now looks for 'detail' rather than 'faultdetail'
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXISCPP-170

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXISCPP-170
    Summary: The fault message name for details should be 'detail' and not 'faultdetail'
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

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

   Assignee: 
   Reporter: Fred Preston

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

Description:
Observation
-----------
Reading the SOAP spec, the fault message name for details is defined as 'detail' and not 'faultdetail'.  For example, 'over the wire', the SOAP message may have the following structure (note that the name for the details message part is 'detail' not 'faultdetail'):-

:
<SOAP-ENV:Fault>
 <faultcode>SOAP-ENV:Server</faultcode>
 <faultstring>There is a fault</faultstring>
 <detail>
  :
 </detail>
</SOAP-ENV:Fault>
:

Currently, a fault message is serialised as shown belw:-

:
<SOAP-ENV:Fault>
 <faultcode>SOAP-ENV:Server</faultcode>
 <faultstring>There is a fault</faultstring>
 <faultdetail>
  :
 </faultdetail>
</SOAP-ENV:Fault>
:

To make the SOAP message comply with the spec, the code in the following files needs to change:-
File: \CWSS\Build\ws-axis\c\src\soap\SoapFault.cpp
Line: (109) pSZ.serialize("<faultdetail>", NULL);
Line: (111) pSZ.serialize("</faultdetail>", NULL);
Line: (146) pSZ.serialize("<faultdetail>", NULL);
Line: (148) pSZ.serialize("</faultdetail>", NULL);

NB: Only need to change what is serialised, don't need to change the variable name(as I think faultdetail is more descriptive that just detail).


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