John You can use the makefault mediator to do this.
<makefault [version="soap11|soap12"]> <code (value="literal" | expression="xpath")/> <reason (value="literal" | expression="xpath")> <node>? <role>? <detail>? </makefault> See sample 5 http://ws.apache.org/synapse/Synapse_Samples.html#Sample5 If you throw an exception from your mediator, that should trigger synapse to use the sequence named "fault": see http://ws.apache.org/synapse/Synapse_Samples.html#Sample4 Paul On 9/19/07, J Bouck <[EMAIL PROTECTED]> wrote: > In synapse 1.0, I am using a custom class mediator in the inSequence > of a proxy service. How do I generate a SOAP fault from the custom > class mediator? Returning false in the class mediator doesn't seem to > do trigger the faultSequence for the proxy service. Throwing > exceptions in the class mediator doesn't seem to trigger the > faultSequence either. I can get the proxy service fault Sequence to > run only if the in Sequence "send" fails, never with the custom class > mediator that precedes the "send". I have looked at sample 510 that > describes what the synapse.xmlneeds to look like for custom class > mediators, but I can't get that example to generate a SOAP Fault > either. Do I need to write directly to the Synapse MessageContext in > the mediator? > ~john > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
