creating fault for non-wcf client

I am using WCF to act as gateway to linux applications, and thus the
client is not a WCF client. I want to return a SOAP fault to the
client - how do I do this?

On Jun 1, 11:43 am, jvshore <jvsh...@earthlink.net> wrote:
> I am using WCF to act as gateway to linux applications, and thus the
> client is not a WCF client. I want to return a SOAP fault to the
> client - how do I do this?

I failed to indicate that the binding is basicHttpBinding and the
client is making calls to the service via SOAP

On Jun 1, 11:49 pm, jvshore <jvsh...@earthlink.net> wrote:
> On Jun 1, 11:43 am, jvshore <jvsh...@earthlink.net> wrote:
>
> > I am using WCF to act as gateway to linux applications, and thus the
> > client is not a WCF client. I want to return a SOAP fault to the
> > client - how do I do this?
>
> I failed to indicate that the binding is basicHttpBinding and the
> client is making calls to the service via SOAP

I think you can serialize the caught exception(SOAP fault) and send
it. I am not sure whether we can serialize all faults in WCF.

On Jun 3, 12:13 am, Aneesh P <anees...@gmail.com> wrote:
> On Jun 1, 11:49 pm, jvshore <jvsh...@earthlink.net> wrote:
>
> > On Jun 1, 11:43 am, jvshore <jvsh...@earthlink.net> wrote:
>
> > > I am using WCF to act as gateway to linux applications, and thus the
> > > client is not a WCF client. I want to return a SOAP fault to the
> > > client - how do I do this?
>
> > I failed to indicate that the binding is basicHttpBinding and the
> > client is making calls to the service via SOAP
>
> I think you can serialize the caught exception(SOAP fault) and send
> it. I am not sure whether we can serialize all faults in WCF.

In case the fault is not serializabel, we can use a custom
[DataContract] which is serializable and can be sent to any client in
XML format. The logic to handle the fault should be in client side -
like parsing the XML and identifying the error details.