I am looking to use Synapse as a proxy for a web service in a simlar fashion to Synapse sample#103. When a WS-policy violation occurs in the proxy inSequence is there a way to return a custom fault rather than the axisFault that is generated in the soapenv namespace? <soapenv:Fault> <faultcode>soapenv:Server</faultcode> <faultstring>Missing wsse:Security header in request</faultstring> <detail /> </soapenv:Fault> I can get my custom soap faults to be returned for the proxy by configuring the faultSequence for the proxyService, but they aren't returned when the WS-Policy is violated in the inSequence (e.g. missing or invalid wsse headers). The proxy faultSequence only seems to be sent when the outSequence fails (e.g.endpoint server port is not open). I tried adding an onError attribute to inSequence for the proxyService but that didn't work. Any ideas? I am willing to write a custom mediator if need be. I would really like to be able to strictly control the soap faults that could ever be returned for security concerns. ~john
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
