Okay, I’ve been testing some solutions today and I came up with something
that works, but it is very ugly.

Turns out that when I set the soap.Fault in the output channel filter it
will send the fault to the client. So if I want to have a input channel that
tests my message and sends a soap fault back to the client, I need to save
the exception in the Context.OperationState of the message and catch that in
the outputchannel to put it in the soapmessage. But now the requested service
still gets executed. So I have to create a bogus service that does nothing
and redirect my inputchannel to that service by creating an instance of
SoapFilterResult and setting the TargetMethod to my bogus service (and
returning that as the ProcessMessage result.

Inputchannel filter code:
public override SoapFilterResult ProcessMessage(SoapEnvelope envelope)
{
    Exception e = new Exception("This is the exception i want to throw");
    envelope.Context.OperationState.Set<Exception>(e);
   
    Type s = typeof(ISRA.Services.BogusService);
    SoapServerMethod method = new SoapServerMethod(s, new
LogicalMethodInfo(s.GetMethod("BogusExecute")));
    SoapFilterResult res = new SoapFilterResult(method);
    return res;
}

outputchannel filter code:
public override SoapFilterResult ProcessMessage(SoapEnvelope envelope)
{
    Exception e = envelope.Context.OperationState.Get<Exception>();
    if (e != null)
    {
        envelope.Fault = e;
    }
    return SoapFilterResult.Continue;
}

Is there someone with a better idea?

Thanks in advance,
Erik

Tried your method to interrupt the SOAP chain and bypass the original web service and it worked fine.  Thanks much!  Have you had any further thoughts on this?

Posted from http://www.topxml.com/renntp using reNNTP: the website based NNTP reader.