Chapter 4. Fuse Standalone

4.1. Supported containers

Fuse standalone 7.7 is supported on the following runtime containers:

  • Spring Boot 1 and Spring Boot 2
  • Apache Karaf
  • Red Hat JBoss Enterprise Application Platform (JBoss EAP)

4.2. New features in Fuse 7.7

The main new features of Fuse standalone in version 7.7 are:

Camel Pulsar component for Spring Boot 2

The camel-pulsar component is now fully supported for Spring Boot 2 (but not for any other container type).

For more information, see the Apache Pulsar component section of the Apache Camel Component Reference.

New allowlist setting for Jackson Data Formats

Fuse 7.7 provides a customized version of the jackson-databind library, which supports an allowlist mechanism for enabling polymorphic deserialization (in combination with the Jackson object mapper functionality). This new feature provides strong additional protection against deserialization security vulnerabilities, by blocking all gadget classes by default.

To configure the allowlist, set the jackson.deserialization.whitelist.packages system property to a comma-separated list of classes and packages. For example, to allow deserialization of the Triangle, Square classes, set the system property as follows: 

-Djackson.deserialization.whitelist.packages=com.example.Triangle,com.example.Square

For more details of this new feature, see the section Jackson ObjectMapper in the Apache Camel Component Reference.

Set Cipher suites for JMX TLS connections on Apache Karaf
The new enabledCipherSuites property lets you specify the cipher suites to use on JMX TLS connections on Apache Karaf.
Advanced Undertow configuration
Configuration of Undertow to allow fine tuning of the XNIO worker and buffer-pool parameters used by the listeners.

4.3. Technology Preview features

The following features of Fuse standalone are Technology Preview only and are not supported in Fuse 7.7:

Camel Weka component for JBoss EAP
For 7.7, the camel-weka component is a technology preview feature only. It is only available for JBoss EAP containers.
Camel Pulsar component for Spring Boot 1 and Apache Karaf

For 7.7, the camel-pulsar component is available as a technology preview for the Spring Boot 1.x and Apache Karaf containers. Camel Pulsar is not available for JBoss EAP.

For more information, see the Apache Pulsar component section of the Apache Camel Component Reference.

Saga EIP
The Saga Enterprise Integration Pattern (EIP) is a technology preview feature and features only the In-Memory Saga service (which is not suitable for a production environments). The LRA Saga service is not supported. For more details, see section Saga EIP of the "Apache Camel Development Guide".

4.3.1. Fuse Tooling support for Apache Camel

Fuse Tooling provides a cross-platform, cross-IDE approach to Camel application development, with Apache Camel language support extensions or plugins for Visual Studio Code, Eclipse IDE, and Eclipse Che.

For Visual Studio Code, you can also add an extension that provides WSDL to Camel Rest DSL support.

Note: These features are already included by default with Fuse Tooling for Red Hat CodeReady Studio.

Visual Studio Code features

Note

VS Code Apache Camel extensions are community features. They are not supported by Red Hat.

The Language Support for Apache Camel extension provides features for Camel URIs, such as the following:

For XML DSL and Java DSL:

  • When you type, the editor provides code completion for Camel components, attributes, and the list of attribute values.
  • When you hover over a Camel component, the editor shows a brief description of the component (from the Apache Camel component reference).
  • As you edit the file, the editor performs an Apache Camel validation check on the Camel code.
  • You can specify a specific Camel Catalog version by selecting File → Preferences → Settings → Apache Camel Tooling → Camel catalog version.
  • You can use "Quick fix" features to address invalid enum values and unknown Camel URI component properties.

For XML DSL only:

  • You can navigate to Camel contexts and routes in the VS Code Outline panel and in the Go > Go to Symbol in File navigation panel.
  • When you type, the editor provides code completion for referenced IDs of direct, direct VM, VM and SEDA components.
  • You can find references for direct and direct VM components in all open Camel files.

For Properties:

  • Completion for Camel component property
  • Diagnostic

The WSDL 2 Camel Rest DSL extension (wsdl2rest implementation) provides WSDL to Camel Rest DSL support. By specifying an existing WSDL file, you can use this extension to generate a Camel Rest DSL + CXF solution for REST-style access. The WSDL file can be located either on your local file system or from an accessible web URL.

To access the Language Support for Apache Camel and WSDL to Camel Rest DSL features, you add one or more extensions.

The Apache Camel Extension Pack installs the following VS Code extensions:

Optionally, you can install the extensions individually.

For more details, see the following readme files:

Eclipse IDE features

The Language Support for Apache Camel Eclipse plug-in provides the following features for Camel URIs:

In the generic Eclipse text editor for both XML DSL and Java DSL:

  • When you type, the editor provides code completion for Camel components, attributes, and the list of attribute values.
  • When you hover over a Camel component, the editor shows a brief description of the component (from the Apache Camel component reference).

When you use the Eclipse XML or Java editor, only the auto-completion feature is provided.

To access the Language Support for Apache Camel features, you install the Eclipse plug-in from the Eclipse Marketplace. For more details, see the readme file for Apache Camel Language Server Protocol for Eclipse IDE.

Eclipse Che features

The Language Support for Apache Camel plugin for Eclipse Che 7 provides features for Camel URIs in XML DSL and Java DSL.

  • When you type, the editor provides code completion for Camel components, attributes, and the list of attribute values.
  • When you hover over a Camel component, the editor shows a brief description of the component (from the Apache Camel component reference).
  • When you save the file, the editor performs an Apache Camel validation check on the Camel code.

To activate this plugin for Eclipse Che, you can use the "Apache Camel based on Spring Boot" stack or edit your workspace configuration.

4.4. BOM files for Fuse 7.7

To configure your Maven projects to use the supported Fuse 7.7 artifacts, use the BOM versions documented in this section.

4.4.1. BOM File

To upgrade your Fuse standalone applications to use the 7.7 dependencies, edit the Maven pom.xml and change the versions of the BOMs and Maven plugins listed in the following table:

Table 4.1. Maven BOM and plugin versions for 7.7 using the BOM

Container TypeMaven BOM or Plugin Artifact groupId/artifactIdVersion for Fuse 7.7

Spring Boot 1

org.jboss.redhat-fuse/fuse-springboot-bom

7.11.1.fuse-sb2-7_11_1-00022-redhat-00002

org.jboss.redhat-fuse/fabric8-maven-plugin

7.11.1.fuse-sb2-7_11_1-00022-redhat-00002

org.jboss.redhat-fuse/spring-boot-maven-plugin

7.11.1.fuse-sb2-7_11_1-00022-redhat-00002

Spring Boot 2

org.jboss.redhat-fuse/fuse-springboot-bom

7.11.1.fuse-sb2-7_11_1-00022-redhat-00002

org.jboss.redhat-fuse/fabric8-maven-plugin

7.11.1.fuse-sb2-7_11_1-00022-redhat-00002

org.jboss.redhat-fuse/spring-boot-maven-plugin

7.11.1.fuse-sb2-7_11_1-00022-redhat-00002

Apache Karaf

org.jboss.redhat-fuse/fuse-karaf-bom

7.11.1.fuse-sb2-7_11_1-00022-redhat-00002

org.jboss.redhat-fuse/karaf-maven-plugin

7.11.1.fuse-sb2-7_11_1-00022-redhat-00002

JBoss EAP

org.jboss.redhat-fuse/fuse-eap-bom

7.11.1.fuse-sb2-7_11_1-00022-redhat-00002

For more details about using the BOM, see Fuse Migration Guide.

4.5. Important notes

Important notes for the Fuse 7.7 release of the Fuse standalone distribution:

Disable the Fuse Console’s proxy servlet when deploying to AWS

If you want to deploy a standalone Fuse application to Amazon Web Services (AWS), you should disable the Fuse Console’s proxy servlet by setting the hawtio.disableProxy system property to true.

Note

When you disable the Fuse Console proxy servlet, the Fuse Console’s Connect tab is disabled and you cannot connect to other JVMs from the Fuse Console. If you want to deploy more than one Fuse application on AWS, you must deploy the Fuse Console for each application.

Spring Boot 1 is deprecated
Spring Boot 1 is deprecated since Fuse 7.7 and will be removed in a future release.