Is it possible to convert a SoapException to a FaultException with WCF?

Question

I am migrating a web service client from WSE to WCF.

I already modified the internal fault and error handling to deal with FaultExceptions instead of SoapExceptions.

The project has an extensive suite of test cases to test the fault and error handling which still relies on SoapException. For various reasons, I'd prefer not to rewrite them all.

Is it possible to just convert the SoapException into a FaultException and thereby running the old test cases against the new error handling code?

Answer 1

how about

catching SoapException and throwing FaultException (a solution, not recommendation)

catch(SoapException)
{
 throw new FaultException(); // something similar
}

Answer 2

You should be able to use EnterpriseLibrary to convert the FaultException to a SoapException at a particular boundary, in this case client proxy.

Answer 3

You can try to implement IErrorHandler Interface. In HandleError method, rethrow exception wrapped to SoapException. Latter you have to register it globally(web.config or whatever).

Example of how this will help (pseudo code):

public SoapErrorHandler : IErrorHandler
{
   public void HandleError(Exception ex)
   {
      throw new SoapException(ex.Message, ex);
   }
}

Answer 4

What about using a message inspector ? Have you checked the IClientMessageInspector ?

It may look like this :

The message inspector

public class MessageInspector : IClientMessageInspector
{
     ...

    #region IClientMessageInspector Members
    public void AfterReceiveReply(ref System.ServiceModel.Channels.Message reply, object correlationState)
    {
      //rethrow your exception here, parsing the Soap message
        if (reply.IsFault)
        {
            MessageBuffer buffer = reply.CreateBufferedCopy(Int32.MaxValue);
            Message copy = buffer.CreateMessage();
            reply = buffer.CreateMessage();

            object faultDetail = //read soap detail here;

            ...
        }
    }
    #endregion

     ...
}

The endpoint behavior

public class MessageInspectorBehavior : IEndpointBehavior
{
     ...

    #region IEndpointBehavior Members
    public void ApplyClientBehavior(ServiceEndpoint endpoint, System.ServiceModel.Dispatcher.ClientRuntime clientRuntime)
    {
        MessageInspector inspector = new MessageInspector();
        clientRuntime.MessageInspectors.Add(inspector);  
    }
    #endregion

     ...
}

http://weblogs.asp.net/paolopia/archive/2007/08/23/writing-a-wcf-message-inspector.aspx

I think a good practice is to use exceptions as faults too.