hanks again,
Bill
Send reply to: "Tomcat Users List" <[EMAIL PROTECTED]>
From: "Yansheng Lin" <[EMAIL PROTECTED]>
To: "'Tomcat Users List'" <[EMAIL PROTECTED]>
Subject:RE: Handling SOAP faults
D
EMAIL PROTECTED]
Sent: April 16, 2004 18:38
To: Tomcat Users List
Subject: RE: Handling SOAP faults
Thanks for the interest and reply Yan, but you make assumptions
that are incorrect:
> Ok, I think what happened here is: the response message is *overwritten*
> since you already defined a c
now, but it's only recently
that people have actually started generating and expecting
SOAPfaults.
>
> -Original Message-
> From: Bill Harrelson [mailto:[EMAIL PROTECTED]
> Sent: April 16, 2004 11:59
> To: Tomcat Users List
> Subject: RE: Handling SOAP faults
il 16, 2004 11:59
To: Tomcat Users List
Subject: RE: Handling SOAP faults
What the SOAP spec says is that a SOAPfault XML document
needs to be returned in the errorStream and a response code of
500 returned.
Sending a response 500 is easy, including a response message is
also easy. But, wh
quot;Yansheng Lin" <[EMAIL PROTECTED]>
To: "'Tomcat Users List'" <[EMAIL PROTECTED]>
Subject:RE: Handling SOAP faults
Date sent: Fri, 16 Apr 2004 11:21:06 -0600
> How about setting the fault on the response? With 500 as stat
How about setting the fault on the response? With 500 as status. Or is
that what you asked for?
-Yan
-Original Message-
From: Bill Harrelson [mailto:[EMAIL PROTECTED]
Sent: April 15, 2004 19:04
To: Tomcat Users List
Subject: Handling SOAP faults
Hello,
I'm using Tomcat 4.2.14, JDK 1
