Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 12284 invoked from network); 9 Feb 2005 10:40:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 9 Feb 2005 10:40:24 -0000 Received: (qmail 15152 invoked by uid 500); 9 Feb 2005 10:40:24 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 15132 invoked by uid 500); 9 Feb 2005 10:40:24 -0000 Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: List-Id: "Apache AXIS C Developers List" Reply-To: "Apache AXIS C Developers List" Delivered-To: mailing list axis-c-dev@ws.apache.org Received: (qmail 15058 invoked by uid 99); 9 Feb 2005 10:40:23 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from ajax-1.apache.org (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 09 Feb 2005 02:40:22 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (8.12.11/8.12.11) with ESMTP id j19AeJYG022674 for ; Wed, 9 Feb 2005 11:40:19 +0100 Message-ID: <348459855.1107945619597.JavaMail.jira@ajax.apache.org> Date: Wed, 9 Feb 2005 11:40:19 +0100 (CET) From: "Samisa Abeysinghe (JIRA)" To: axis-c-dev@ws.apache.org Subject: [jira] Updated: (AXISCPP-259) WSDL faults not being deserialised In-Reply-To: <1263424732.1100255006550.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 [ http://issues.apache.org/jira/browse/AXISCPP-259?page=history ] Samisa Abeysinghe updated AXISCPP-259: -------------------------------------- Component: Deserialization (was: Serialization) > WSDL faults not being deserialised > ---------------------------------- > > Key: AXISCPP-259 > URL: http://issues.apache.org/jira/browse/AXISCPP-259 > Project: Axis-C++ > Type: Bug > Components: Deserialization > Reporter: Andrew Perry > > The FaultMappingDoc test is not getting the expected output. The WSDL has 3 faults defined, DivByZeroStruct, OutOfBoundsStruct and SpecialDetailStruct. The test calls the MathOps service 4 times, 1 with valid values and the other 3 times to get the faults thrown. The services are hosted on WebSphere rather than the Axis Server, but from the response message you can see that the correct faults are being thrown. The first call works, the second to get a DivByZeroStruct fault sort of works in that a MathOpsService Exception is thrown but none of the fault detail is shown, but the final 2 requests which should also have MathOpsService exceptions get an unspecified exception in that 'catch(...)' catches it rather than either MathOpsService_AxisClientException or AxisException. > Client output > loop 0 > trying to div 10 and 5 > Result is 2 > loop 1 > trying to div 10 and 0 > MathOpsService Exception: AxisTransportException:HTTP transport error Internal Server Error > loop 2 > trying to div 1000 and 5 > Unspecified Exception: > loop 3 > trying to div 10 and -5 > Unspecified Exception: > on-the-wire response > -------------------- > HTTP/1.1 200 OK^M > Server: WebSphere Application Server/5.1^M > Content-Type: text/xml; charset=utf-8^M > Content-Language: en-GB^M > Transfer-Encoding: chunked^M > ^M > 197^M > > 2^M > 0^M > ^M > HTTP/1.1 500 Internal Server Error^M > Server: WebSphere Application Server/5.1^M > Content-Type: text/xml; charset=utf-8^M > Content-Language: en-GB^M > Transfer-Encoding: chunked^M > ^M > 2fb^M > > ns2008922717:DivByZeroStructDivision by zero exception110.52^M > 0^M > ^M > HTTP/1.1 500 Internal Server Error^M > Server: WebSphere Application Server/5.1^M > Content-Type: text/xml; charset=utf-8^M > Content-Language: en-GB^M > Transfer-Encoding: chunked^M > ^M > 31a^M > > ns2008922717:SpecialDetailStructYou have entered 1000 for the first parameter. 1000 is reserved. Please do not use it^M > 0^M > ^M > ----------------------------- > Is it possible to get the soap fault detail? > Why do the last 2 faults not get caught by the Axis Exceptions? -- 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