Chapter 1. Creating a New Fuse Integration Project

download PDF


Creating a new Fuse Integration project involves these main steps:

After you configure the project, the tooling downloads all of the required Maven dependencies and creates the POM file needed to run and publish the project.


The first time that you build a Fuse project in CodeReady Studio, it might take several minutes for the wizard to finish generating the project as it downloads dependencies from remote Maven repositories.

Before you begin

Before you create a new Fuse Integration project, you should have the following information:

  • Your target runtime environment: Fuse on OpenShift or Fuse standalone (Spring Boot, Fuse on Karaf, or Fuse on EAP)
  • The Camel version (if other than the default used by the tooling)

Specifying the project name and workspace

To create a new Fuse Integration project, follow these steps:

  1. Select New Project Red Hat Fuse Fuse Integration Project to open the New Fuse Integration Project wizard.

    The wizard opens with the Use default workspace location option selected in the Location pane.

  2. In Project Name, type a name for the new project, for example MySampleProject.
  3. Specify the workspace location in which you want to store the data for the project.

    • To use the default workspace, leave the Use default workspace location option enabled.
    • To use an alternative location clear the Use default workspace location option and specify a location in the Path field.

      Click BrowseButton to quickly find and select an alternate workspace.

  4. Click Next to open the Select a Target Environment page.

Configuring the project deployment environment

When you create a new project, you specify the project’s target deployment environment so that your project has the resources it needs at runtime. You must select a deployment platform and a Camel version. Optionally, you can specify a runtime configuration.

With the Select a Target Environment page open:

  1. Select whether you want to deploy the project on Kubernetes/OpenShift or on a Standalone platform.


    If you select Kubernetes/OpenShift for the deployment platform, the Sprint Boot runtime is automatically selected and you can skip to Step 3.

  2. If you select Standalone for the deployment platform:

    1. Choose a target runtime environment:

      • Spring Boot
      • Karaf/Fuse on Karaf
      • Wildfly/Fuse on EAP
    2. For the Karaf and EAP standalone runtime environments, choose one of the following options for the runtime configuration:

  3. In the Select the Camel version for your new project pane, accept the default Camel version associated with the runtime or change the default by:

    • Selecting a Camel version from the drop-down list. Fuse Tooling supports the listed productized versions.
    • Typing a different Camel version if you want to experiment with non-productized versions (that are not supported).

      You can click the Verify button to check whether the tooling can access the specified version. If not, a notification similar to the following example appears in the Select a Target Runtime page header:


      After you create, configure, and save a project, you can change the Camel version. See Chapter 12, Changing the Camel version.

  4. After you choose a runtime environment and a Camel version on which to base your new Fuse Integration project, click Next to open the wizard’s Advanced Project Setup page and then follow the steps in the section called “Selecting a project template”.

Creating a new target runtime (optional)

For the Karaf and EAP standalone runtime environments, you can optionally create a new runtime configuration from the New Fuse Integration Project wizard.

  1. From the wizard’s the Select a Target Runtime page, click New to open the New server runtime environment page:

    New Server Runtime Environment
  2. Expand the Red Hat JBoss Middleware folder, and then select a Red Hat Fuse runtime environment.

    Leave the Create a new local server option unchecked. You can create the local server later when you are ready to publish your project (see Section 28.1, “Adding a Server”).


    If you check the Create a new local server option, the New Fuse Integration Project wizard walks you through additional steps to define and configure the Fuse server runtime (as described in Section 28.1, “Adding a Server”). Then, when it builds the project, it also adds the server runtime to the Servers view in the Fuse Integration perspective.

  3. Click Next to open the server’s New Server Runtime Environment page:

  4. Specify the Name, Home Directory, Execution Environment of the server runtime:

    • Name — Accept the default or enter a new name for the runtime environment.
    • Home Directory — Click the Browse button to locate and select the server runtime’s installation directory.


      If the server is not already installed on your machine, you can install it now by clicking the Download and install runtime link and then following the site’s download instructions. Depending on the site, you might be required to provide valid credentials before you can continue the download process.

    • Runtime JRE: Execution Environment — Accept the default or select another JavaSE version from the drop-down list.

      If the version that you want does not appear on the list, click the Environments button and select the version from that list. The JRE version that you select must be installed on your machine.


      Fuse 7.x requires JRE version 1.8.

    • Runtime JRE: Alternate JRE - If your project requires a different version of Java, you can use this option.
  5. Click Finish to return to the New Fuse Integration Project wizard’s Select a Target Runtme page:

    The newly configured target runtime appears in the Target Runtime pane’s drop-down menu, and the Camel version supported by the runtime appears in the Camel Version pane, grayed out.

    After you create a Fuse Integration project, it is possible to change the Camel version. See Chapter 12, Changing the Camel version.

  6. Click Next to specify a template for the project as described in the section called “Selecting a project template”.

Selecting a project template

The Advanced Project Setup page provides a list of templates that you can use as a starting point for your new project. The templates, based on common use cases, provide sample code and data to get you started quickly. The list of available templates depends on the runtime environment that you selected on the previous page. Select a template to view its description in the right pane.


If you do not see a template that meets your requirements, you can click the Where can I find more examples to use as templates? link to open an information dialog with a list of URLs with more examples:


To use one of these examples:

  1. Select Cancel to exit the New Fuse Integration Project wizard.
  2. Clone the repository from one of the listed URLs.
  3. Import the example project into CodeReady Studio as described in Chapter 13, Importing an existing Maven project.
  • For Fuse on OpenShift there is a single template that demonstrates how to configure Camel routes in Spring Boot using a Spring XML configuration file. This template creates a Fuse Integration project and requires a Camel version newer than 2.18.1.redhat-000012.

    This template creates a project that runs on OpenShift servers, and it supports the Spring DSL only. For details on using this template, see Chapter 7, Getting Started with Fuse on OpenShift.

  • For Wildfly or Fuse on EAP there is a single template that provides a sample Camel route that calls into a bean service to say "Hello". This template creates a project that runs on Red Hat EAP servers, and it supports the Spring DSL only.

  • For Karaf or Fuse on Karaf, you have a choice of templates. You can create an empty project, which creates a skeleton Camel context routing file based on one of the three supported Domain Specific Languages (DSLs), or you can use a predefined template, each of which is based on a common use case. Individual templates might not support all DSL options.


    For Java DSL, the tooling generates a file that you can edit in the tooling’s Java editor, but it does not generate a graphical diagram representation of it.

    • Content Based Router — Provides a sample Camel route that reads files from a specific location and routes them to different output folders according to message content.

      This template creates a project that runs on Red Hat Fuse servers, and it supports all three of the DSLs.

    • CXF code first — Provides a sample Camel route that is started by a CXF web service call.

      This template creates a project that runs on Red Hat Fuse servers, and it supports the Spring and Java DSLs only.

      1. Select a template from the list.
      2. Click Finish.

        The tooling starts building the project and adds it to the Project Explorer view.

        If the Fuse Integration perspective is not already open, the tooling asks whether you want to switch to it now:

      3. Click Yes to open the new project in the Fuse Integration perspective:


        The project appears in the Project Explorer view. By default, the project includes an Apache Camel context (XML) file.

      4. Click the Source tab at the bottom of the canvas to see the generated Camel context file:


If you want to add another new Camel context file to the project, see Chapter 11, Creating a New Camel XML file.

When you build a project that uses CXF you might want the build process to automatically operate on the Java files to generate WSDL files. To do this, configure the java2ws Maven plug-in in the project’s .pom file. See: Apache CXF Development Guide, Maven Tooling Reference, java2ws.

Resolving Maven dependency errors

You might encounter Maven dependency errors after you create a new Fuse Integration project.

Though it can happen at other times, it more typically occurs when you cancel a project build before the process has finished. Interrupting the process in this way often prevents all of the project’s dependencies from downloading from the Maven repositories, which can take some time.

You can often resolve these dependency errors by updating Maven dependencies as follows:

  1. In the Project Explorer view, right-click the root project to open the context menu.
  2. Select Maven Update Project.
  3. In the Update Maven Project wizard:

    • Select the project that you want to update, if more than one appears in the wizard’s list.
    • Click the Force Update of Snapshots/Releases option to enable it.
  4. Click OK.

    In the bottom, right corner of the workbench, you can view the progress status bar churning as missing dependencies are downloaded from the Maven repositories.

Red Hat logoGithubRedditYoutubeTwitter


Try, buy, & sell


About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.