Menu Close
Settings Close

Language and Page Formatting Options

Chapter 4. Fuse Standalone

4.1. Supported containers

Fuse standalone 7.6 is supported on the following runtime containers:

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

4.2. New features in Fuse 7.6

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

Fuse is supported on EAP in domain mode
See the Installing on JBoss EAP guide for information on starting JBoss EAP in domain mode.
Fuse on Apache Karaf supports dynamic <expression-filter> statements

For Fuse on Karaf, you can now use an expression-filter in your Undertow subsystem to restrict IP addresses for incoming connections for web applications.

For more information on how to restrict IP addresses for incoming connections for web applications, see this Red Hat solution: https://access.redhat.com/solutions/3476101

4.3. Technology Preview features

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

The Camel Pulsar component is not supported on all container types
For 7.6, the camel-pulsar component is a technology preview feature only. It is available for Spring Boot 1.x, Spring Boot 2.x, and Apache Karaf containers but not for JBoss EAP containers.

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

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.

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.6

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

4.4.1. BOM File

To upgrade your Fuse standalone applications to use the 7.6 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.6 using the BOM

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

Spring Boot 1

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

7.6.0.fuse-760027-redhat-00001

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

7.6.0.fuse-760027-redhat-00001

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

7.6.0.fuse-760027-redhat-00001

Spring Boot 2

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

7.6.0.fuse-sb2-760028-redhat-00001

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

7.6.0.fuse-sb2-760028-redhat-00001

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

7.6.0.fuse-sb2-760028-redhat-00001

Apache Karaf

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

7.6.0.fuse-760027-redhat-00001

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

7.6.0.fuse-760027-redhat-00001

JBoss EAP

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

7.6.0.fuse-760027-redhat-00001

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

4.5. Important notes

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

Fuse on EAP is upgraded to use JBoss EAP 7.2.3 (from JBoss EAP 7.2)
The Fuse 7.6 release runs on the JBoss Enterprise Application Platform (EAP) 7.2.3 container (upgraded from JBoss EAP 7.2 in the previous release of Fuse). For more details, see JBoss EAP 7.2.0 Release Notes.
ENTESB-2344: Camel Jetty/Http4 producers should respect content-length/transfer-encoding:chunked headers
A client that sends a request to the Apache Camel proxy gateway expects that Apache Camel keeps the same chunking (or non-chunking) behavior that was specified in the original request. If the content-length is set incorrectly with chunking encoding, you may see undefined behavior.
ENTESB-10923: camel-linkedin quickstart is removed

The camel-linkedin component was removed in Fuse 7.5. The camel-linkedin quickstart was removed in Fuse 7.6.

Important

Although removed from Fuse 7.5, the camel-linkedin component is likely to be restored in a later release.