Spring Integration has eg. gateway beans that have auto-startup attribute indicating whether the integration route gateway should be initially started or not. Fabric3 does not seem to respect this attribute at all and these gateway beans are always started at startup regardless of auto-startup attribute.
Attached is a simple sample project (based on Fabric3 Spring sample fabric3-samples-spring-restcalc 1.9) which demonstrates this feature. If using the junit test in the module the integration route (gateway) is not started until manually done so in test method. But when deployed to Fabric3 the route is started at startup and every 5 seconds a message is printed into console. It should work so that user has to call the restful web service (eg. /calculator/1+1) in order to start the integration route.