Handling connectivity issues in web service outbound gateway (retry)

[ach]

Hello
At a glance it seems like you need this one: https://jira.springsource.org/browse/INT-1685

Yes, this would seem to fit my requirements. Unfortunately, this is needed for current development so I can probably not wait for 2.2 to be released.

So, try to investigate this sample: https://github.com/SpringSource/spri...ed/dynamic-ftp

Spawning multiple application contexts seems a bit... heavyweight for our purposes. We've also run into production issues related to dynamically instantiating app contexts in the past, so that's probably a no-go.

Just to reiterate: Basically, the idea is that we will be using this pattern in multiple places in the application (and potentially in other apps as well):

1. Make a WS call
2. If the endpoint is down, queue the message for retry (persistent queue)
3. Poll the queue and retry the WS call

If I wanted to implement the above for multiple endpoints in the same application, I would need to copy/paste a giant chunk of XML configuration for each one. So, I want to encapsulate that pattern for re-use.

I have tried to programmatically create the SI objects and wire them together but it is proving to be difficult.

[ach]

I apologize for bumping this again... is it feasible to programmatically create these components and wire them together, for the sake of reuse? Is there a resource (other than the API docs) that might be able to help me with this?