Return-Path: Delivered-To: apmail-ws-axis-c-user-archive@www.apache.org Received: (qmail 86558 invoked from network); 4 Dec 2009 03:58:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Dec 2009 03:58:03 -0000 Received: (qmail 92653 invoked by uid 500); 4 Dec 2009 03:58:03 -0000 Delivered-To: apmail-ws-axis-c-user-archive@ws.apache.org Received: (qmail 92577 invoked by uid 500); 4 Dec 2009 03:58:01 -0000 Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C User List" Reply-To: "Apache AXIS C User List" Delivered-To: mailing list axis-c-user@ws.apache.org Received: (qmail 92568 invoked by uid 99); 4 Dec 2009 03:58:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Dec 2009 03:58:01 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of dimuthuc@gmail.com designates 209.85.222.203 as permitted sender) Received: from [209.85.222.203] (HELO mail-pz0-f203.google.com) (209.85.222.203) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Dec 2009 03:57:50 +0000 Received: by pzk41 with SMTP id 41so3700742pzk.0 for ; Thu, 03 Dec 2009 19:57:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type; bh=VEgYvUUH3Pxe9BfOw7fuDXrfvv+fBJBwEHqaAb/4zuU=; b=DFjoCH7XOJJSxUToABTor5tUANi6cu6jCew9bFlbrGVY8PQzsHT1gA7r4XKb70s9MQ DrQE2RHJEQ4CevMJUJq7fyzDSsMrD+a8AG4T90SF1hyaDTs34rRCAN9DZFIKUMyKdUQv HlB4YgTkeKMZ225Fa2ZXu4LnJDHmvzzgXHjPY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=Yw870/JR47ISdfa/h1ezj3EvtnawqfUFe6qw2X3XB4ODGlZSbhtxJxyhBGNdIWcwcj FNE9ElyX3YHbAZ/i8XIvpNX7P/nd1D6GBi8mV6DKEmkBQVFe/buUu06jJE3mZHUh1ZZB Hk7nH6sk6O6U92iOvRVBbUQkE1QYsNrsS6bXM= MIME-Version: 1.0 Received: by 10.143.20.7 with SMTP id x7mr321928wfi.53.1259899047074; Thu, 03 Dec 2009 19:57:27 -0800 (PST) In-Reply-To: References: From: Dimuthu Gamage Date: Fri, 4 Dec 2009 09:27:07 +0530 Message-ID: Subject: Re: using faults w/ wsdl2c To: Apache AXIS C User List Content-Type: multipart/alternative; boundary=001636e1f8f5275b110479df1b40 X-Virus-Checked: Checked by ClamAV on apache.org --001636e1f8f5275b110479df1b40 Content-Type: text/plain; charset=ISO-8859-1 Hi, If you use the latest axis2 WSDL2C generator code, you don't need to create soap fault message manually as the generated code provide lot of support in generating fault message. Please have a look at this for the improved API, http://www.dimuthu.org/blog/2009/02/09/code-generate-custom-soap-faults-for-axis2c/ Thanks Dimuthu On Wed, Nov 18, 2009 at 3:49 AM, Doug Price wrote: > While I see that this approach allows the creation of user-defined fault > types, is it possible to also use it to specify the standard SOAP-ENV:Fault? > I see a struct named axiom_soap_fault_t in the distribution, but I can't > seem to return it from the axis2_svc_skel_*_on_fault() function because it > requires a pointer to the SOAP body to create one. Is there some other way > to return a standard SOAP fault from a service? > > > -- > Doug Price > Research Director | Presagis > > T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399 > > DISCLAIMER: This e-mail message is for the sole use of the intended > recipient(s) and may contain confidential and/or proprietary information. Do > not read, copy, or disseminate this message unless you are the addressee. > Any unauthorized review, use, disclosure or distribution is strictly > prohibited. If you have received this message in error, please contact the > sender by reply e-mail and delete the original and any copies from your > system. > > -----Original Message----- > > From: Amir Mousavizadegan [mailto:amir.mousavizadegan@cox.net] > Sent: Tuesday, November 17, 2009 10:29 AM > To: Apache AXIS C User List > Subject: Re: using faults w/ wsdl2c > > I did not write the sample codes nor the document, however in order to > get it working, you have to change the body of the generated code, or > create a replacement function as I did. > thx > Amir > ----- Original Message ----- > From: "Doug Price" > To: "Apache AXIS C User List" > Sent: Tuesday, November 17, 2009 11:05 AM > Subject: RE: using faults w/ wsdl2c > > > Just what I was looking for. Thanks so much. > > A quick follow up question on the code though. Is there a reason that > axis2_svc_skel_Division_on_fault() doesn't use the adv_divFault api to > create the fault? > > > -- > Doug Price > Research Director | Presagis > > T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399 > > DISCLAIMER: This e-mail message is for the sole use of the intended > recipient(s) and may contain confidential and/or proprietary information. > Do > not read, copy, or disseminate this message unless you are the addressee. > Any unauthorized review, use, disclosure or distribution is strictly > prohibited. If you have received this message in error, please contact the > sender by reply e-mail and delete the original and any copies from your > system. > > -----Original Message----- > > From: Amir Mousavizadegan [mailto:amir.mousavizadegan@cox.net] > Sent: Tuesday, November 17, 2009 7:52 AM > To: Apache AXIS C User List > Subject: Re: using faults w/ wsdl2c > > Please see attached document > ----- Original Message ----- > From: "Doug Price" > To: > Sent: Monday, November 16, 2009 4:47 PM > Subject: using faults w/ wsdl2c > > > I created a simple web service w/ Axis2c using wsdl2c on a WSDL file I > created in Eclipse. The default functionality of this works fine. > However, > now I'd like to incorporate faults into my SOAP messages. I created a > fault > type in my WSDL and wsdl2c creates the wrappers for the fault message, but > the service skeleton and client stubs files seem to hard coded to assume no > faults are ever sent / received. For example, the client axis2_stub_op_*() > function takes my request message type and returns my response message > type, > but doesn't seem to account for my fault type. Modifying the code, I can > see that the fault is received and correctly deserialized, but I'll have to > continually hand edit the axis2_stub*.c and my client.c file as I make > modifications to my WSDL in order to make this work. > > The same is true on the service side w/ the axis2_skel*() functions. Am I > missing something here, or are faults not supported w/ wsdl2c? > > -- > Doug Price > Research Director | Presagis > > T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399 > > DISCLAIMER: This e-mail message is for the sole use of the intended > recipient(s) and may contain confidential and/or proprietary information. > Do > not read, copy, or disseminate this message unless you are the addressee. > Any unauthorized review, use, disclosure or distribution is strictly > prohibited. If you have received this message in error, please contact the > sender by reply e-mail and delete the original and any copies from your > system. > > > > -- Thanks, Dimuthu Gamage http://www.dimuthu.org http://www.wso2.org --001636e1f8f5275b110479df1b40 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

If you use the latest axis2 WSDL2C generator code, you don't= need to create soap fault message manually as the generated code provide l= ot of support in generating fault message.

Please have a look at thi= s for the improved API, http://www.dimuthu.org/blog/20= 09/02/09/code-generate-custom-soap-faults-for-axis2c/


Thanks
Dimuthu


On Wed, Nov= 18, 2009 at 3:49 AM, Doug Price <Doug.Price@presagis.com> wrote:
While I see that this approach allows the creation of user-defined fault ty= pes, is it possible to also use it to specify the standard SOAP-ENV:Fault? = =A0I see a struct named axiom_soap_fault_t in the distribution, but I can&#= 39;t seem to return it from the axis2_svc_skel_*_on_fault() function becaus= e it requires a pointer to the SOAP body to create one. =A0Is there some ot= her way to return a standard SOAP fault from a service?


--
Doug Price
Research Director | Presagis

T. +1 972 943.2433 =A0F. +1 469 467.4564 =A0C. +1 469 867.8399

DISCLAIMER: This e-mail message is for the sole use of the intended recipie= nt(s) and may contain confidential and/or proprietary information. Do not r= ead, copy, or disseminate this message unless you are the addressee. Any un= authorized review, use, disclosure or distribution is strictly prohibited. = If you have received this message in error, please contact the sender by re= ply e-mail and delete the original and any copies from your system.

-----Original Message-----

From: Amir Mousavizadegan [mailto:amir.mousavizadegan@cox.net]
Sent: Tuesday, November 17, 2009 10= :29 AM
To: Apache AXIS C User List
Subject: Re: using faults w/ wsdl2c

I did not write the sample codes =A0nor the document, =A0however =A0in orde= r to
get it working, you have to change the body of the generated =A0code, or create a replacement function as I did.
thx
Amir
----- Original Message -----
From: "Doug Price" <Doug.Price@presagis.com>
To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>
Sent: Tuesday, November 17, 2009 11:05 AM
Subject: RE: using faults w/ wsdl2c


Just what I was looking for. =A0Thanks so much.

A quick follow up question on the code though. =A0Is there a reason that axis2_svc_skel_Division_on_fault() doesn't use the adv_divFault api to<= br> create the fault?


--
Doug Price
Research Director | Presagis

T. +1 972 943.2433 =A0F. +1 469 467.4564 =A0C. +1 469 867.8399

DISCLAIMER: This e-mail message is for the sole use of the intended
recipient(s) and may contain confidential and/or proprietary information. D= o
not read, copy, or disseminate this message unless you are the addressee. Any unauthorized review, use, disclosure or distribution is strictly
prohibited. If you have received this message in error, please contact the<= br> sender by reply e-mail and delete the original and any copies from your
system.

-----Original Message-----

From: Amir Mousavizadegan [mailto:amir.mousavizadegan@cox.net]
Sent: Tuesday, November 17, 2009 7:52 AM
To: Apache AXIS C User List
Subject: Re: using faults w/ wsdl2c

Please see attached document
----- Original Message -----
From: "Doug Price" <Doug.Price@presagis.com>
To: <axis-c-user@ws.apache.= org>
Sent: Monday, November 16, 2009 4:47 PM
Subject: using faults w/ wsdl2c


I created a simple web service w/ Axis2c using wsdl2c on a WSDL file I
created in Eclipse. =A0The default functionality of this works fine. =A0How= ever,
now I'd like to incorporate faults into my SOAP messages. =A0I created = a fault
type in my WSDL and wsdl2c creates the wrappers for the fault message, but<= br> the service skeleton and client stubs files seem to hard coded to assume no=
faults are ever sent / received. =A0For example, the client axis2_stub_op_*= ()
function takes my request message type and returns my response message type= ,
but doesn't seem to account for my fault type. =A0Modifying the code, I= can
see that the fault is received and correctly deserialized, but I'll hav= e to
continually hand edit the axis2_stub*.c and my client.c file as I make
modifications to my WSDL in order to make this work.

The same is true on the service side w/ the axis2_skel*() functions. =A0Am = I
missing something here, or are faults not supported w/ wsdl2c?

--
Doug Price
Research Director | Presagis

T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399

DISCLAIMER: This e-mail message is for the sole use of the intended
recipient(s) and may contain confidential and/or proprietary information. D= o
not read, copy, or disseminate this message unless you are the addressee. Any unauthorized review, use, disclosure or distribution is strictly
prohibited. If you have received this message in error, please contact the<= br> sender by reply e-mail and delete the original and any copies from your
system.






--
Thanks,
= Dimuthu Gamage

http://www.dimuthu= .org
http://www.wso2.org
--001636e1f8f5275b110479df1b40--