I assume you're referring to "Polling Consumer". This action already makes a synchronous call to the target endpoint.
Can you elaborate please?
"Polling Consumer" is the correct name. :)
I was thinking about asynchronous calls. I'll be consuming a service, but I don't know wheter it's accessible or not. So I'd like to retain the messages until the service is accessible.
It can't do this at the moment. Anyway, I think that type of functionality should be more generally available (via something like the dead letter queue perhaps? Kurt?) instead of building it directly into a component such as the SOAPClient.