Yes, Theoretically it is possible to do the timeout using RM and take the control over the timeout to send the SOAPFault through an RMListner.
But I have not tried this on Synapse and also to do this we need some minor improvements on Synapse code. Let me try this and get back to you. As Asankha said, this seems like a good feature if we can get this done...... Thanks, Ruwan. On 4/3/07, Asankha C. Perera <[EMAIL PROTECTED]> wrote:
Hi Bouck Right now or with the 0.91 release, you cannot set a timeout on an endpoint to throw a fault after a specific delay. However I see this as a possibility even with the new asynchronous http/s transports, if we include it as a feature. I am not sure, but there may be a way to do this with Sandesha2 (the WS-RM implementation) as well through policy.. maybe Ruwan could reply on it asankha J Bouck wrote: > I am new to synapse and am working my way through the samples (0.91). I > have a nagging question about how quality-of-service policies should be > configured in synapse when using proxies. > For example, I want synapse to do something like proxy SOAP over HTTP. I > want a rule that the remote endpoint has 5 seconds to return a > response or > synapse with throw the SOAP fault itself to let the client know that > there > are issues. Do I configure synapse as a proxy and use some sort of > WS-ReliableMessaging policy? Do I write a custom mediator to > implement this > timeout policy? What would the configuration look like? > ~jb > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Ruwan Linton http://www.wso2.org - "Oxygenating the Web Services Platform"
