You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-user@ws.apache.org by Asaf Lahav <as...@primagrid.com> on 2006/08/15 11:48:19 UTC
RE: Not getting Custom Fault
Yes...
-----Original Message-----
From: Daniel Jemiolo [mailto:danjemiolo@us.ibm.com]
Sent: Tuesday, July 25, 2006 6:02 PM
To: muse-user@ws.apache.org
Subject: RE: Not getting Custom Fault
Well, Muse and/or Axis has to know how to serialize the AddFault class
that you've created - I'm wondering what system is in place to explain how
to map AddFault objects to:
<tns:AddFault>
<wsbf:Timestamp/>
<wsbf:OriginReference/>
<tns:YourCustomField/>
...
</tns:AddFault>
Otherwise, I imagine Axis would just turn the exception into a SOAP fault
per usual - is that the kind of XML you're getting?
Dan
Asaf Lahav <as...@primagrid.com> wrote on 07/25/2006 12:32:05 PM:
> The Fault Elemement definition I'm using is as follows:
>
>
>
>
>
> <element name="AddFault">
>
> <complexType>
>
> <complexContent>
>
> <extension base="wsbf:BaseFaultType"/>
>
> </complexContent>
>
> </complexType>
>
> </element>
>
>
>
> wsbf is an alias for -->
>
<http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-BaseFaults-1.2-draft-01.xsd
> >
>
http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-BaseFaults-1.2-draft-01.xsd
>
>
>
> I defined the web service operation like this:
>
> <operation name="Add">
>
> <input message="tns:AddRequest"/>
>
> <output message="tns:AddResponse"/>
>
> <fault name="AddFault" message="tns:ObtainGroupsListFault"/>
>
> </operation>
>
> The messages:
>
> <message name="AddRequest">
>
> <part name="parameter" element="tns:AddRequest"/>
>
> </message>
>
> <message name="AddResponse">
>
> <part name="parameter" element="tns:Add Response"/>
>
> </message>
>
> <message name="AddFault">
>
> <part name="parameter" element="tns:Add Fault"/>
>
> </message>
>
>
>
> I don't understand what you mean by mapping system?
>
>
>
>
>
> -----Original Message-----
> From: Daniel Jemiolo [mailto:danjemiolo@us.ibm.com]
> Sent: Tuesday, July 25, 2006 5:22 PM
> To: muse-user@ws.apache.org
> Subject: Re: Not getting Custom Fault
>
>
>
> can you send the output you are seeing, what your WSDL/schema looks like
>
> (the fault definition in particular), and explain the mapping system you
>
> are using to declare the fault class as the one to be serialized on the
>
> wire? I'm not very familiar with how Muse 1.x handles custom fault
>
> serialization, so please show the mapping that is used to tell Muse
about
>
> the fault class.
>
>
>
> Dan
>
>
>
>
>
>
>
> Asaf Lahav <as...@primagrid.com> wrote on 07/25/2006 11:10:00 AM:
>
>
>
> > Hi all,
>
> >
>
> > What could be the reason I'm not getting a Custom Fault for a MUSE Web
>
> Servicefunction?
>
> > I have a MUSE web service that has a function "Add" which may throw an
>
> > "AddFault" if any exception occurs.
>
> > What could be the reason the Client (Consumer) is not getting the
proper
>
>
>
> > "AddFault" response even though it is thrown by the web service
>
> function?
>
> >
>
> > Thanks in advance,
>
> > Asaf
>
> ---------------------------------------------------------------------
>
> To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
>
> For additional commands, e-mail: muse-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org