Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 53628 invoked from network); 12 Nov 2006 06:03:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Nov 2006 06:03:09 -0000 Received: (qmail 47698 invoked by uid 500); 12 Nov 2006 06:03:12 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 46698 invoked by uid 500); 12 Nov 2006 06:03:10 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 46687 invoked by uid 99); 12 Nov 2006 06:03:10 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Nov 2006 22:03:10 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of ONURAL@nortel.com designates 47.140.192.56 as permitted sender) Received: from [47.140.192.56] (HELO zrtps0kp.nortel.com) (47.140.192.56) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Nov 2006 22:02:55 -0800 Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com [47.129.230.99]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id kAC62W607387 for ; Sun, 12 Nov 2006 01:02:32 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C70620.242EA0C8" Subject: Using standard wsdl:fault with extended faultcodes Date: Sun, 12 Nov 2006 01:02:31 -0500 Message-ID: <87AC5F88F03E6249AEA68D40BD3E00BE0C534133@zcarhxm2.corp.nortel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Using standard wsdl:fault with extended faultcodes Thread-Index: AccGICPGNgl2abrLTbSuq/51n41u/Q== From: "Gul Onural" To: X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C70620.242EA0C8 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, I am trying to use wsdl standard (WSDL 1.1, SOAP 1.1) fault in my wsdl as it is defined in http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383507. faultcode=20 faultstring=20 faultactor=20 detail=20 There are small set of SOAP Fault Codes defined under http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383510. For example the following faultcodes are defined in the spec : VersionMismatch MustUnderstand Client Server I want to use faultcode to set more detailed fault codes, such as Client.Authentication, etc... I want to be able to explicitly define these faultCodes in my wsdl, so that client would know exactly what to expect. What I am trying to do is not really custom fault, but I am looking for a way to let the client programmatically know what to expect in faultcode, by specifying the "extended faultcodes" in my wsdl. Then client would inspect faultcode to take proper action. Does anybody know how to do this ? How would operation look like in this case : Gul ------_=_NextPart_001_01C70620.242EA0C8 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Using standard wsdl:fault with extended faultcodes

Hi,

I am trying to use wsdl standard (WSDL = 1.1, SOAP 1.1) fault in my wsdl as it is defined in <= FONT COLOR=3D"#0000FF" SIZE=3D2 = FACE=3D"Arial">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc47838350= 7.

faultcode
faultstring
faultactor
detail

There are small set of SOAP Fault Codes = defined under <= FONT COLOR=3D"#0000FF" SIZE=3D2 = FACE=3D"Arial">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc47838351= 0.
For example the following faultcodes = are defined in the spec :

VersionMismatch
MustUnderstand
Client
Server

I want to use faultcode to set more = detailed fault codes, such as Client.Authentication, etc…
I want to be able to explicitly define = these faultCodes in my wsdl, so that client would know exactly what to = expect.
What I am trying to do is not really = custom fault, but I am looking for a way to let the client = programmatically know
what to expect in faultcode, by = specifying the "extended faultcodes" in my wsdl. Then client = would inspect faultcode
to take proper action.

Does anybody know how to do this ? How = would operation look like in this case :
<operation name=3D"op1">
         = <input message=3D"op1Request"/>
         = <output message=3D"op1Response"/>
         = <fault name=3D"op1fault" message=3D"What to specify here ?"/>
</operation>

Gul



------_=_NextPart_001_01C70620.242EA0C8--