xml-soap-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel P Allen" <dal...@nist.gov>
Subject RE: Handling SOAP Faults using HTTPURLConnection based client
Date Thu, 06 Jun 2002 11:29:41 GMT

	Your welcome Swami.

	I never fought this battle.  I was using 1.4 at work and discovered
	the problem when I ran my SOAP client from home using 1.3.1-02.  I
	simply installed 1.4 at home ;-)  I assume you have tried catching
	the exception and plowing ahead with a getInputStream() call? Good
	luck!  BTW - 1.3 is real trash IMNSHO!

	Dan

-----Original Message-----
From: K. Swaminathan [mailto:swami@instantis.com]
Sent: Wednesday, June 05, 2002 5:50 PM
To: soap-user@xml.apache.org
Subject: RE: Handling SOAP Faults using HTTPURLConnection based client


Thanks Dan,

 but is there any trick we can do to retrieve the fault data using 1.3 at
all?

Swami K.

->
->	This unfriendly behavior of HttpURLConnection seems to have been
->	corrected, errr... changed, in J2SE 1.4.
->
->	Dan
->
->-----Original Message-----
->From: K. Swaminathan [mailto:swami@instantis.com]
->Sent: Tuesday, June 04, 2002 10:05 PM
->To: soap-user@xml.apache.org
->Subject: Handling SOAP Faults using HTTPURLConnection based client
->
->
->Hi,
->
-> I am trying to write a simple SOAP client using HttpUrlConnection. If the
->server response
->is a SOAP Fault, then The HttpURLConnection seems to throw a
->FileNotFoundException, when
->attempting to do a conn.getResponseCode(). How does one get access to the
->fault information.
->Some example that I saw on the web, suggested
->conn.getErrorStream(), but it
->returns null.
->Can someone point me to how you read in the fault info?
->
->Thanks
->Swami K.
->
->
->



Mime
View raw message