Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 68926 invoked from network); 15 Aug 2007 10:10:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Aug 2007 10:10:08 -0000 Received: (qmail 72986 invoked by uid 500); 15 Aug 2007 10:10:05 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 72958 invoked by uid 500); 15 Aug 2007 10:10:05 -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 72947 invoked by uid 99); 15 Aug 2007 10:10:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Aug 2007 03:10:05 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Aug 2007 10:09:51 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id BBB157141E2 for ; Wed, 15 Aug 2007 03:09:30 -0700 (PDT) Message-ID: <16861594.1187172570764.JavaMail.jira@brutus> Date: Wed, 15 Aug 2007 03:09:30 -0700 (PDT) From: "Jamie Lyon (JIRA)" To: axis-c-dev@ws.apache.org Subject: [jira] Commented: (AXIS2C-665) "axis2_svc_client_get_last_response_has_fault" return 0 even when there is really soap fault returned. In-Reply-To: <15608681.1186656462910.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 [ https://issues.apache.org/jira/browse/AXIS2C-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519915 ] Jamie Lyon commented on AXIS2C-665: ----------------------------------- I'm not sure about the original poster, but it seems to me as though this problems only occurs when rampart is enabled with a required incoming security header. From what I can determine, when rampart doesn't detect a security header attached to the fault it puts a message in the log. I'm not sure whether this will then affect the outcome from get_last_response_has_fault. But I can certainly make the fault appear and disappear simply by enabling and disabling rampart in axis2.xml. > "axis2_svc_client_get_last_response_has_fault" return 0 even when there is really soap fault returned. > ------------------------------------------------------------------------------------------------------ > > Key: AXIS2C-665 > URL: https://issues.apache.org/jira/browse/AXIS2C-665 > Project: Axis2-C > Issue Type: Bug > Components: core/clientapi > Affects Versions: 1.0.0 > Environment: Windodw Server 2003, English Version, Microsoft Visual C++.net 2005, Intel Petium D CPU 3.0G dual core, 2G memory > Reporter: Rock Wang > Priority: Critical > > "axis2_svc_client_get_last_response_has_fault" return 0 even when there is really soap fault returned. > I have used "axiom_node_to_string" to print the returned soap body by the peer service(which is developed by Java and deployed by JBoss), and it reads: > env:ClientCannot find child element: String_1 > But "axis2_svc_client_get_last_response_has_fault" really returns 0 on it. :-( -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-c-dev-help@ws.apache.org