Chapter 4. Fuse Standalone
4.1. Supported containers
Fuse standalone 7.9 is supported on the following runtime containers:
- Spring Boot 2 (standalone)
- Apache Karaf
- Red Hat JBoss Enterprise Application Platform (JBoss EAP)
4.2. New features in Fuse 7.9
The main new features of Fuse standalone in version 7.9 are:
- Configuration of undertow thread pool names
Undertow thread pools and their names can now be configured on a per-service/bundle basis to improve monitoring and debugging from the Hawtio console.
For more information, see the Worker IO configuration section of the Apache Karaf Security Guide.
- Implement consumer priority in Camel
Some brokers (and Artemis in particular) allow you to specify consumer priority for the messages you are sending. In Fuse 7.9 this configuration option is exposed in the
camel-amqp
andcamel-jms
components.For more information, see the JMS Component section of the Apache Camel Component Reference.
- Support for Salesforce Bulk API V2
The Camel SAP Salesforce Bulk 2.0 API is now supported and can be used to quickly load a large amount of data into Salesforce, or query a large amount of data from Salesforce.
For more information, see the Bulk 2.0 API section of the Apache Camel Component Reference.
- Support for fast RFC serialization in the Camel SAP component
The
camel-sap
component now supports fast RFC serialization.For more information, see the Destination Configuration section of the Apache Camel Component Reference.
- Support Spring Security for Fuse on Karaf
-
The
camel-spring-security
component is now supported.
4.3. Technology Preview features
The following features of Fuse standalone are Technology Preview only and are not supported in Fuse 7.9:
- 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
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:
- You can navigate to endpoints 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 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
andSEDA
components. -
You can find references for
direct
anddirect 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:
- Readme for Apache Camel Extension Pack
- Readme for Apache Camel Language Server Protocol for Visual Studio Code
- Readme for WSDL to Camel Rest DSL
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.9
To configure your Maven projects to use the supported Fuse 7.9 artifacts, use the BOM versions documented in this section.
4.4.1. BOM File
To upgrade your Fuse standalone applications to use the 7.9 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.9 using the BOM
Container Type | Maven BOM or Plugin Artifact groupId/artifactId | Version for Fuse 7.9 |
---|---|---|
Spring Boot 2 |
|
|
|
| |
|
| |
Apache Karaf |
|
|
|
| |
JBoss EAP |
|
|
For more details about using the BOM, see the Migration Guide.
4.5. Important notes
Important notes for the Fuse 7.9 release of the Fuse standalone distribution:
- Fuse on EAP is upgraded to use JBoss EAP 7.4.0 (from JBoss EAP 7.3.2)
- The Fuse 7.9 release now runs on the JBoss Enterprise Application Platform (EAP) 7.4 container (upgraded from JBoss EAP 7.3.2 in the previous release of Fuse). For more details, see JBoss EAP 7.4.0 Release Notes.
- Updated Jackson libraries
- Updated the Jackson libraries from 2.9 and 2.10 to 2.12.1.
- Using OpenJDK 8u292 with Apache Karaf
- When running Fuse in Apache Karaf, Red Hat recommend using OpenJDK 8u282. Do not use OpenJDK 8u292 which has a known issue affecting the credential store.
- Upgrading Fuse on Karaf
The Fuse 7.9 release restores the Apache Karaf mechanism (removed in Fuse 7.8) which enables you to apply fixes to an Apache Karaf container without needing to reinstall an updated version of Fuse on Karaf.
For more details on upgrading to Fuse 7.9 on Karaf, see Fuse Migration Guide.