Chapter 4. Fuse Standalone
4.1. Supported containers
Fuse standalone 7.5 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.5
The main new features of Fuse standalone in version 7.5 are:
- You can now upgrade EAP without needing to reinstall
- Previously in Fuse 7.x, you needed to reinstall EAP to upgrade which required a re-deployment. From Fuse 7.5, you can apply a hot patch to successfully upgrade. See how to do this in the Installing a Fuse hotfix patch on JBoss EAP section of the "Installing on JBoss EAP".
4.3. Technology Preview features
The following features of Fuse standalone are Technology Preview only and are not supported in Fuse 7.5:
- 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 the following features for Camel URIs:
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.
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,VMandSEDAcomponents. -
You can find references for
directanddirect VMcomponents 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:
- 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 and XML DSL only.
- 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 need to edit your workspace’s configuration. For details on how to activate it, see this Red Hat Developers blog entry.
4.4. BOM files for Fuse 7.5
To configure your Maven projects to use the supported Fuse 7.5 artifacts, use the BOM versions documented in this section.
4.4.1. BOM File
To upgrade your Fuse standalone applications to use the 7.5 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.5 using the BOM
| Container Type | Maven BOM or Plugin Artifact groupId/artifactId | Version for Fuse 7.5 |
|---|---|---|
| Spring Boot 1 |
|
|
|
|
| |
|
|
| |
| Spring Boot 2 |
|
|
|
|
| |
|
|
| |
| Apache Karaf |
|
|
|
|
| |
| JBoss EAP |
|
|
For more details about using the BOM, see Fuse Migration Guide.
4.5. Important notes
Important notes for the Fuse 7.5 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.5 release now 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-10923: camel-linkedin quickstart is not working
The
camel-linkedincomponent has been removed in Fuse 7.5.ImportantAlthough removed from Fuse 7.5, the
camel-linkedincomponent is likely to be restored in a later release.
