Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 41268 invoked from network); 25 Jun 2005 02:20:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 25 Jun 2005 02:20:59 -0000 Received: (qmail 73110 invoked by uid 500); 25 Jun 2005 02:20:47 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 73085 invoked by uid 500); 25 Jun 2005 02:20:47 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 73072 invoked by uid 99); 25 Jun 2005 02:20:47 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Jun 2005 19:20:47 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of davanum@gmail.com designates 64.233.170.207 as permitted sender) Received: from [64.233.170.207] (HELO rproxy.gmail.com) (64.233.170.207) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Jun 2005 19:20:47 -0700 Received: by rproxy.gmail.com with SMTP id 34so137093rns for ; Fri, 24 Jun 2005 19:20:44 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Kj4MD5aegiuYuQne5wmY4+VZdgQSdAK4R0FfGTuORSEDC7CRMSxosRCEwVYYStGC7d45z0gLU6ax+j0Pz72Cz9sF5IBZASl1yj1acAmJbodgNEq764UH58qRmu4YNQv26WIF8/FvqOGtZeoteKdvbpl/tvDVWt7se/zMg3WPS6Q= Received: by 10.38.103.16 with SMTP id a16mr105524rnc; Fri, 24 Jun 2005 19:20:44 -0700 (PDT) Received: by 10.38.8.28 with HTTP; Fri, 24 Jun 2005 19:20:44 -0700 (PDT) Message-ID: <19e0530f05062419205858c116@mail.gmail.com> Date: Fri, 24 Jun 2005 22:20:44 -0400 From: Davanum Srinivas Reply-To: dims@apache.org To: axis-dev@ws.apache.org Subject: Re: SOAPMessage vs. SOAPException in SOAPConnectionImpl In-Reply-To: <20050625020901.GA5882@django> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20050625020901.GA5882@django> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N try=20 "return new Message(af);" instead of "throw new SOAPException(af);" and see if that helps. -- dims On 6/24/05, David Blevins wrote: > Hey all, >=20 > Dealing with a very interesting failure. It seems that anytime you use = a SOAPConnection to make a call, you only get a fault back if the the serve= r sent it. Anything that would be a valid fault as per the WSI basic profi= le is rewrapped as a SOAPException and the fault codes are lost. >=20 > SOAPConnectionImpl.java > ----------------------------- > public SOAPMessage call(SOAPMessage request, Object endpoint) throws = SOAPException { > ... > try { > Call call =3D new Call(endpoint.toString()); > ... > call.invoke((Message) request); > return call.getResponseMessage(); > } catch (java.net.MalformedURLException mue){ > throw new SOAPException(mue); > } catch (org.apache.axis.AxisFault af){ > throw new SOAPException(af); > } > } > ----------------------------- >=20 > Shouldn't this code create a SOAPMessage containing the fault rather than= rewrap and throw it as a SOAPException? >=20 > Thanks, > David >=20 --=20 Davanum Srinivas -http://blogs.cocoondev.org/dims/