Unless I'm doing something wrong here, it also looks like our ESB configuration won't start not only if a jms-provider isn't available, but also if any of our JMSRouter actions can't connect on startup. Is this by design? If so that seems like a fundamental flaw in the design. Why should one failed connection cause an entire configuration to not be initialized? Throwing an exception I could understand, but a complete failure of startup?