Return-Path: 
 <axis-dev-return-50661-apmail-ws-axis-dev-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-dev-archive@www.apache.org
Received: (qmail 60373 invoked from network); 12 Oct 2006 01:52:22 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 12 Oct 2006 01:52:22 -0000
Received: (qmail 43692 invoked by uid 500); 12 Oct 2006 01:52:20 -0000
Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org
Received: (qmail 43648 invoked by uid 500); 12 Oct 2006 01:52:20 -0000
Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
list-help: <mailto:axis-dev-help@ws.apache.org>
list-unsubscribe: <mailto:axis-dev-unsubscribe@ws.apache.org>
List-Post: <mailto:axis-dev@ws.apache.org>
List-Id: <axis-dev.ws.apache.org>
Delivered-To: mailing list axis-dev@ws.apache.org
Received: (qmail 43629 invoked by uid 99); 12 Oct 2006 01:52:19 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Oct 2006 18:52:19 -0700
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Oct 2006 18:52:18 -0700
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 5ADD07142DD
	for <axis-dev@ws.apache.org>; Wed, 11 Oct 2006 18:51:37 -0700 (PDT)
Message-ID: <23080384.1160617897369.JavaMail.jira@brutus>
Date: Wed, 11 Oct 2006 18:51:37 -0700 (PDT)
From: "Davanum Srinivas (JIRA)" <jira@apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Resolved: (AXIS2-1052) Complex fault detail lost in
 exception caught on client side
In-Reply-To: <16021980.1156152494556.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

     [ http://issues.apache.org/jira/browse/AXIS2-1052?page=all ]

Davanum Srinivas resolved AXIS2-1052.
-------------------------------------

    Resolution: Fixed

Should be fixed. Please let us know if it isn't and we can reopen this issue.

thanks,
dims

> Complex fault detail lost in exception caught on client side
> ------------------------------------------------------------
>
>                 Key: AXIS2-1052
>                 URL: http://issues.apache.org/jira/browse/AXIS2-1052
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: databinding
>    Affects Versions: 1.0
>         Environment: Windows XP  SP2 / Tomcat 5.5
>            Reporter: Richard Gruet
>         Assigned To: Eran Chinthaka
>            Priority: Critical
>
> (This bug description started in AXIS2-917, but it was judged more appropriate to open a new issue since this is related to fault handling implementation, not documentation).
> If I define a custom fault with a *complex* structure, like this one:
> <complexType name="MiFault">
>         <sequence>
>         <element name="error" minOccurs="0" maxOccurs="unbounded">
>            <complexType>
>              <sequence>
>                 <element name="errCode" type="string" minOccurs="0" />
>                 <element name="errMsg" type="string" />
>                 <element name="parameter" type="string" minOccurs="0" />
>               </sequence>
>            </complexType>
>         </element>
>       </sequence>
>   </complexType>
> ... assuming that I defined an operation throwMiFault() and generated the code from the WSDL, Axis2 will have generated a ThrowMiFaultFaultException class. 
> When I raise a ThrowMiFaultFaultException  instance from the throwMiFault method, everything goes fine on the server side. But on the client side, when catching the ThrowMiFaultFaultException, I found that the fault detail (obtained via e.getFaultMessage()) has an empty 'error' array [please see details in AXIS2-917]. However, the XML for the fault detail looks correct:
> <xml-fragment xmlns:axis2ns1="http://linedata.com/WS/tests/sampleService/parts/1.0">
>   <axis2ns1:error>
>     <axis2ns1:errCode>CODE1</axis2ns1:errCode>
>     <axis2ns1:errMsg>Error #1 message text</axis2ns1:errMsg>
>     <axis2ns1:parameter>param#1</axis2ns1:parameter>
>   </axis2ns1:error>
>   <axis2ns1:error>
>     <axis2ns1:errCode>CODE2</axis2ns1:errCode>
>     <axis2ns1:errMsg>Error #2 message text</axis2ns1:errMsg>
>   </axis2ns1:error>
> </xml-fragment> 
> ... which suggests a possible AXIOM error (Derek Foster suggested that it might be related to AXIS2-928). 
> When I define a *simple* custom error like this one:
>   <element name='xxxFault'>
>     <complexType>
>       <sequence>
>         <element name='message' type='string'/>
>       </sequence>
>     </complexType>
>   </element> 
> ... everything works fine and the xxxFaultException I get on the client side contains the error detail (i.e. the message element). So the problem seems to occur only with complex fault detail.
> Richard

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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org