axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Doug Price <Doug.Pr...@presagis.com>
Subject RE: using faults w/ wsdl2c
Date Tue, 17 Nov 2009 22:19:15 GMT
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" <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.  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" <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.  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.




Mime
View raw message