Hi Daniel, anonymous wrote : | Now, if the validation fails (step 1) we can set the FaultTo to let the calling system know somethings wrong. | If the posting to the WebService fails for some reason (step 2) it make sense to try to redeliver at a later time. | So far so good :) anonymous wrote : | We would like to be able to have different scheduling intervals for different action pipelines and thought that step 2's exception handler would add the message to the MessageStore with a classification specific to that action pipeline. | The redeliverService is configured in the jbossesb.esb, and there is only one. It looks for msgs in the RDLVR classification, and tries to redeliver them on it's configured schedule. So all services share the same redeliverService. I never thought you'd like to make the redeliver schedule different for different services. That said, like you said, we can define other redeliverDeliver services, and make the classification configurable. Then we could set that classification in the message and the ServiceInvoker could look to see if that property is set and if so use it. Can you explain a little more why you would need different redeliver schedules? --Kurt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074400#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...