Show Table of Contents Hide Table of Contents English English Multi-page HTML Single-page HTML PDF ePub Deploying into Spring Boot1. Getting Started with Spring Boot1.1. Overview of the circuit breaker booster1.2. Prerequisites1.3. Generate the booster project1.4. Build and run the booster2. Deployment Options2.1. Standalone deployment2.2. OpenShift deployment3. Building with Maven3.1. Generating a Maven project3.1.1. Project generator at launch.openshift.io3.1.2. Fuse tooling wizard in Developer Studio3.2. Depend on the BOM for Spring Boot3.2.1. BOM file for Spring Boot3.2.2. Spring Boot Maven plugin4. Apache Camel in Spring Boot4.1. Introduction to Camel Spring Boot4.2. Introduction to Camel Spring Boot Starter4.3. Auto-configured Camel context4.4. Auto-detecting Camel routes4.5. Camel properties4.6. Custom Camel context configuration4.7. Disabling JMX4.8. Auto-configured consumer and producer templates4.9. Auto-configured TypeConverter4.10. Spring type conversion API bridge4.11. Disabling type conversions features4.12. Adding XML routes4.13. Adding XML Rest-DSL4.14. Testing with Camel Spring Boot4.15. See Also4.16. Using Spring Boot, Apache Camel and external messaging brokers4.16.1. Using an external messaging broker.A. Preparing to use MavenA.1. OverviewA.2. PrerequisitesA.3. Adding the Red Hat Maven repositoriesA.4. ArtifactsA.5. Maven coordinatesB. Spring Boot Maven Plug-InB.1. Spring Boot Maven Plugin OverviewB.2. GoalsB.3. UsageLegal Notice Deploying into Spring Boot Red Hat Fuse 7.0Building and running Spring Boot applications in standalone mode Fuse Documentation Team email@example.com Legal NoticeAbstract This guide explains how to build Spring Boot applications that are packaged as Jar files and run directly in a JVM (standalone mode). 1. Getting Started with Spring Boot Where did the comment section go?Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.