We have a use case that retrieves message off of JMS queue utilizing the message-driven-channel-adapter, transform and aggregates the messages and eventually delivery aggregated messages to third party via web service.
The third party web service requires we authenticate and retrieve a token before we start delivery of data.
Our thoughts were to have the application retrieve a token during start up. Our issue is that if this fails for some reason we do not want the message-driven-channel-adapter to start up and pull messages off the JMS queue.
We have tried setting the depends-on value for the container associated with message-driven-channel-adapter. This seems to work partially except that is causing the entire application to not start on failure.
Is it possible to only have a failure prevent the one message-driven-channel-adapter from starting up??