Release Notes for Red Hat Fuse 7.6
What's new in Red Hat Fuse
Abstract
Chapter 1. Fuse 7.6 Product Overview
1.1. Fuse distributions
Fuse 7.6 is provided in the form of three different distributions, as follows:
- Fuse standalone
The classic distribution of Fuse, supported on multiple operating systems. This distribution is supported for the following container types:
- Apache Karaf
- JBoss Enterprise Application Platform (EAP)
- Spring Boot
- Fuse on OpenShift
The distribution of Fuse for running integration applications on OpenShift (supported on the Red Hat Enterprise Linux operating system). In this case, the supported container types are provided in the form of docker-formatted container images:
- Java image (for Spring Boot)
- Apache Karaf image
- JBoss EAP image
- Fuse Online
The distribution of Fuse for non-expert integrators with a simplified workflow accessed through a browser based UI. This distribution is available for the following kinds of deployment:
- Pre-installed on the OpenShift Online Professional tier
- On a Red Hat Managed Integration cluster
- For installation on an on-premises OpenShift cluster
1.2. New features
Fuse 7.6 includes several major component upgrades and a large selection of new features. For details, consult the new features sections for each of the Fuse distributions:
1.3. Supported Configurations
For information about supported configurations, standards, and components in version 7.6, see the following Customer Portal articles:
Chapter 2. Fuse Online
Fuse Online provides a web browser interface that lets a business expert integrate two or more different applications or services without writing code. It also provides features that allow the addition of code if it is needed for complex use cases.
Fuse Online runs an integration on OpenShift as a Spring Boot application that uses Apache Camel. As a Technology Preview feature, Camel K is available as an additional runtime.
2.1. About Fuse Online distributions
Fuse Online is Red Hat’s web-based integration platform. Syndesis is the open source project for Fuse Online. Fuse Online runs in these OpenShift environments:
| Host Environment | Installation |
|
OpenShift Online | Red Hat installs and provisions Fuse Online on Red Hat infrastructure. |
| OpenShift Container Platform | Customer installs and manages. |
2.2. New features in Fuse Online 7.6
Fuse Online 7.6 provides the following new features:
The following connectors, which were Technology Preview features in the previous release, are now supported:
- Amazon DynamoDB lets you retrieve data from an Amazon DynamoDB table, add data to a DynamoDB table, or remove data from a DynamoDB table.
- Box lets you connect to a Box server to download or upload a file.
- MongoDB lets you obtain content from a MongoDB database or update content in a MongoDB database.
- Fuse Online now provides enhanced activity tracking (based on Jaeger). Enhanced activity tracking is now enabled by default, when you install Fuse Online on OCP from the command line.
- OpenAPI 3.0 as well as OpenAPI 2.0 is now supported for creating REST API client connectors and API provider integrations.
2.3. Changes in Fuse Online 7.6
Fuse Online 7.6 changes Fuse Online 7.5 features as follows:
Changes to the data mapper:
Mapping from or to a field in a nested collection is now supported. When a source field is nested in a number of collections you can map it to a target field that meets one of these conditions:
- The target field is nested in the same number of collections as the source field.
- The target field is nested in only one collection.
While a conditional expression in a data mapping continues to be a Technology Preview feature, a conditional expression can now:
- Refer to a field that is in a collection.
- Specify any transformation supported by the data mapper.
-
Specify the
LT()(less than) function to obtain the smaller of two numbers or theTOLOWER()function to convert a string to lowercase.
Changes for Fuse Online environments that run on OpenShift Container Platform on-site:
-
The Fuse Online installation download package now provides a default custom resource file,
default-cr.yml, which you can edit before you install Fuse Online. Edits can enable add-on features and/or change default configuration values. You can install a default Fuse Online environment by running the installation script without editingdefault-cr.yml. For details, see Installation of Fuse Online on OCP. - You can now enable automatic discovery of Kafka brokers (AMQ Streams instances), which makes configuring a Kafka connection easier because the UI can display the broker URL details. See Enabling auto-discovery of Kafka brokers/AMQ Streams.
- Procedures for backing up and restoring Fuse Online environments are now documented. See Managing Fuse Online on OCP.
-
The Fuse Online installation download package now provides a default custom resource file,
2.4. Upgrading Fuse Online integrations
The Fuse Online upgrade process depends on whether Fuse Online is installed on Red Hat OpenShift Online or on OpenShift Container Platform (OCP).
- OpenShift Online - When Fuse 7.6 is released, the Fuse Online infrastructure on OpenShift Online is automatically upgraded. You must republish any running integrations as described in Upgrading Fuse Online integrations that are running on OpenShift Online.
- OCP - To upgrade a Fuse Online environment that is running on OpenShift Container Platform on-site, you must download the latest Fuse Online release, run the update script, and then republish any running integrations as described in Upgrading Fuse Online on OCP.
2.5. Important notes for Fuse Online
Important notes for the Fuse 7.6 release of the Fuse Online distribution:
The following limitations apply when the Camel K runtime is installed with Fuse Online:
- Fuse Online extensions are not supported by the Camel K runtime.
Extensions are not displayed in the Fuse Online user interface under Customizations.
Note that Camel K runtime is a Technology Preview feature.
- Enhanced activity tracking is not available, if you install Fuse Online from OperatorHub (see the Fuse Online section of Known Issues). To take advantage of enhanced activity tracking in this release, we recommend that you install Fuse Online using the command-line script instead. See Installing Fuse Online on OCP for details.
- In this release, connections to Kafka do not support SSL. It is expected that this will change in a future release.
- When Fuse Online is installed and provisioned on Red Hat infrastructure, the account is limited to a specific number of integrations that can be running at one time. For details, see the pricing plan. If you are using a Fuse Online evaluation account, then only one integration at a time can be running.
- An OpenAPI schema that you upload to Fuse Online might not define input/output types. When Fuse Online creates a custom API client from an OpenAPI schema that does not specify input/output types then it is not possible to create an integration that maps integration data to fields that the API client can process or from fields that the API client processed. If an integration requires data mapping to or from a custom API, then when you upload the OpenAPI schema, click Review/Edit to open API Designer, which is an API editing tool, and add input/output type specifications.
- An OpenAPI document that you use for a custom API client connector or for an API provider integration cannot have cyclic schema references. For example, a JSON schema that specifies a request or response body cannot reference itself as a whole nor reference any part of itself through any number of intermediate schemas.
2.6. Obtaining technical support for Fuse Online
To obtain technical support, in the Fuse Online console, in the left navigation panel, click Support. Use the Support page to download diagnostic information for all integrations or for one or more integrations that you choose. The page also provides a link for opening a support ticket and providing the diagnostic information that you downloaded.
2.7. Technology Preview features in Fuse Online
This release includes the Technology Preview features that are listed below.
Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information, see Red Hat Technology Preview features support scope.
Data virtualization
For Fuse Online environments that run on OpenShift Container Platform on-site, data virtualization is a container-native service. It integrates data from multiple heterogeneous sources, including relational databases, files, web services, and SaaS repositories. In Fuse Online, developers can create a virtual database image that defines a custom, logical view of their source data. They can then deploy that image on OpenShift. Applications connect to the virtual database over a standard OData, REST, or JDBC interface, and can run SQL queries across all of the data sources, even those that do not support SQL.
To enable data virtualization, see Installation of Fuse Online on OCP.
- The Knative connector lets you connect to a Knative channel to obtain or send messages, expose the integration as a Knative service, or call a Knative service.
Conditional expressions for mapping data fields
In the data mapper, you can specify a conditional expression and apply it to one data mapping. For example, a conditional expression can specify evaluation of a source field and how to populate the target field if the source field is empty. The limited set of expressions that you can specify are similar to Microsoft Excel expressions.
Camel K is available as an additional runtime.
To enable Camel K, see Installation of Fuse Online on OCP.
For a REST API client that uses OAuth, when you create an API client connector, you can change the default OAuth2 behavior of connections that you create from that connector. Fuse Online vendor extensions to the OpenAPI specification support the following:
- Providing client credentials as parameters.
- Obtaining a new access token based on HTTP response status codes.
Chapter 3. Fuse on OpenShift
Fuse on OpenShift enables you to deploy Fuse applications on OpenShift Container Platform.
3.1. Supported version of OpenShift
Fuse on OpenShift is now supported on OpenShift Container Platform 4.x. For details of the supported version (or versions) of OpenShift Container Platform to use with Fuse on OpenShift, see the Supported Configurations page.
3.2. Supported images
Fuse on OpenShift provides the following Docker-formatted images:
-
fuse7/fuse-java-openshift— Spring Boot -
fuse7/fuse-karaf-openshift— Apache Karaf -
fuse7/fuse-eap-openshift— Red Hat JBoss Enterprise Application Platform -
fuse7/fuse-console— Fuse console -
fuse7/fuse-console-operator— Fuse console operator -
fuse7/fuse-apicurito— Apicurito REST API editor -
fuse7/fuse-apicurito-generator— Apicurito REST application generator -
fuse7-tech-preview/fuse-apicurito-operator— API Designer Operator
3.3. New features in Fuse 7.6 on OpenShift
Fuse on OpenShift provides following new features in version 7.6:
- Spring Boot 2 runtime is now supported on OpenShift.
- Fuse on OpenShift is now supported on OpenShift 4.x.
Fuse Console operator
Fuse Console operator simplifies the procedures for installing, upgrading, and uninstalling the Fuse Console on OpenShift. For details of how to use the Fuse Console operator, see Set up the Fuse Console.
NoteIn order to keep the connection between the Fuse Console proxy and the Jolokia agent secure, it is necessary to generate, sign and deploy a client certificate. This must be done manually, as an admin procedure, after installing Fuse Console on OCP 4.x.
3.4. Technology Preview features
The following features of Fuse on OpenShift are Technology Preview only and are not supported in Fuse 7.6:
- Data Virtualization
- Red Hat Data Virtualization is a container-native data virtualization service, based on the Teiid data virtualization project. Red Hat Data Virtualization combines data from multiple heterogeneous sources, such as relational databases, files, web services, and SaaS repositories. For more details, see Using Data Virtualization.
- API Designer operator installation
- You can install the API Designer operator from the Operator Hub of OpenShift Container Platform 4.x. The API Designer operator provides you access to a Technology Preview of the API Designer operator for Fuse on OpenShift. The API Designer operator simplifies the procedures for installing, upgrading, and uninstalling API Designer on OpenShift. For details on how to install the API Designer operator, see Installing Fuse Imagestreams and Temaplates on the OpenShift 4.x Server.
Neither the API Designer operator nor the API Designer instance that it installs are supported. This technology preview feature is not suitable for testing on a production environment.
3.5. Important notes
Important notes for the Fuse 7.6 release of the Fuse on OpenShift distribution:
- Container Development Kit (CDK) 3.10 is the recommended version for use with Fuse 7.6 on OpenShift 3.11
We recommend that developers use CDK 3.10 to try out applications on OpenShift 3.11. CDK is not available for OpenShift 4.x.
NoteCDK is provided only as a convenience for developers and is not a supported OpenShift distribution.
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-pulsarcomponent 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,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 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:
| Container Type | Maven BOM or Plugin Artifact groupId/artifactId | Version for Fuse 7.6 |
|---|---|---|
| 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.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-linkedincomponent was removed in Fuse 7.5. Thecamel-linkedinquickstart was removed in Fuse 7.6.ImportantAlthough removed from Fuse 7.5, the
camel-linkedincomponent is likely to be restored in a later release.
Chapter 5. Deprecated and Removed Features
If you need any assistance or have any questions about the upcoming changes in Fuse 7, contact support@redhat.com.
5.1. Deprecated
The following features are deprecated in Fuse 7.6 and may be removed in a future release:
- PHP, Python, and Ruby scripting languages are deprecated in Camel applications
- The PHP, Python, and Ruby scripting languages are deprecated in Camel applications since Fuse 7.4 and will be removed in a future release. The Camel community has deprecated PHP, Python, and Ruby since Camel 2.19 (see CAMEL-10973). This applies to all Fuse containers types: Apache Karaf, JBoss EAP, and Spring Boot.
- HP-UX OS is deprecated
- The HP-UX operating system is deprecated since Fuse 7.2 and support for this operating system could be removed in a future release of Fuse. In particular, note that the JBoss EAP 7.2 container has already dropped support for HP-UX and, consequently, any future version of Fuse on JBoss EAP that runs on JBoss EAP 7.2 will not be supported on HP-UX.
- Camel MQTT component is deprecated
- The Camel MQTT component is deprecated in Fuse 7.0 and will be removed in a future release of Fuse. You can use the Camel Paho component instead, which supports the MQTT messaging protocol using the popular Eclipse Paho library.
- Camel LevelDB component is deprecated on all operating systems except for Linux
-
Since Fuse 6.3, the Camel LevelDB (
camel-leveldb) component is deprecated on all operating systems except for Red Hat Enterprise Linux. In future, the Camel LevelDB component will be supported only on Red Hat Enterprise Linux. - BatchMessage class from the Camel SJMS component is deprecated
- The BatchMessage class from the Camel SJMS component is deprecated in Fuse 7 (deprecated in Apache Camel since version 2.17) and may be removed from a future version of Apache Camel and Fuse.
5.2. Removed in Fuse 7.5
The following features were removed in Fuse 7.5:
- Support for integration with MS SQL Server 2014 has been dropped in 7.5
- MS SQL Server 2014 is no longer tested and supported for integrations with Fuse 7.5. We recommend that you use one of the more recent versions of MS SQL Server instead — for example, MS SQL Server 2016 or 2017.
- Camel LinkedIn component has been removed in 7.5
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.
5.3. Removed in Fuse 7.3
The following features were removed in Fuse 7.3:
- Camel YQL component has been removed in 7.3
- The Camel YQL component has been removed in Fuse 7.3.
- OpenJPA and OpenJPA3 Karaf features have been blacklisted in 7.3
-
The
openjpafeature and theopenjpa3feature have been blacklisted (removed) from the Apache Karaf container in 7.3. For a Java Persistence Architecture (JPA) implementation, use the supportedhibernatefeature instead. - camel-jetty Karaf feature has been blacklisted in 7.3
-
The
camel-jettyfeature has been blacklisted (removed) from the Apache Karaf container in 7.3, because it uses Jetty 8. Use thecamel-jetty9feature instead. - pax-jms-oracleaq Karaf feature has been blacklisted in 7.3
-
The
pax-jms-oracleaqfeature has been blacklisted (removed) from the Apache Karaf container in 7.3, because it requires 3rd party, non-free Oracle AQ libraries. - camel-elasticsearch component has been removed from Fuse on EAP (Wildfly Camel) in 7.3
-
The
camel-elasticsearchcomponent has been removed from Fuse on EAP (Wildfly Camel) in 7.3. Use the newercamel-elasticsearch-restcomponent instead.
5.4. Removed in Fuse 7.2
The following features were removed in Fuse 7.2:
- Camel XMLRPC component has been removed in 7.2
- The Camel XMLRPC component has been removed in Fuse 7.2.
- Camel Netty component has been removed in 7.2
- The Camel Netty component has been removed in Fuse 7.2. It is recommended that you use the Camel Netty4 component instead.
5.5. Removed in Fuse 7.0
The following features were removed in Fuse 7.0:
- Support for Red Hat JBoss Operations Network (JON) has been removed in 7.0
- Since Fuse 7.0, Fuse on Karaf no longer supports JON and no longer provides JON plugins for integrating with the JON runtime.
- Embedded ActiveMQ broker has been removed in 7.0
- Since Fuse 7.0, Fuse on Karaf no longer provides an embedded ActiveMQ Broker. Customers should connect to a supported remote broker directly. For more information on our supported brokers, refer to the "Supported Messaging Providers" section of the Red Hat Fuse Supported Configurations page.
- Fuse integration pack has been removed in 7.0
- Support for running rules and processes is provided by components shipped with Red Hat JBoss BPM Suite and Red Hat JBoss BRMS.
- Karaf console commands for child container administration have been removed in 7.0
Since Fuse 7.0, the Karaf console commands for child container administration are not supported. That is, the console commands prefixed by
instance:(Karaf 4.x syntax) and the console commands prefixed byadmin:(Karaf 2.x syntax) are not supported.NoteIn the Fuse 7.0 GA release, the
instance:commands are not blacklisted. This is a known issue.- SwitchYard has been removed in 7.0
- Since Fuse 7.0, SwitchYard has been removed, and you should use Apache Camel directly instead. For more detailed information, see the knowledge base article, SwitchYard Support Plan After Releasing Fuse 7.
- Support for Fabric8 1.x has been removed in 7.0
Since Fuse 7.0, Fabric8 v1 has been replaced by Fuse on OpenShift (previously, Fuse Integration Services), which includes components of Fabric8 v2 technology. Fuse on OpenShift provides a set of tools and Docker-formatted images that enable development, deployment, and management of integration microservices within OpenShift.
Although Fuse on OpenShift has a different architecture, it fulfills the same provisioning, automation, central configuration and management requirements that Fabric8 v1 provides. For more information, see Fuse on OpenShift Guide.
- Camel components for Google App Engine have been removed in 7.0
-
The Camel components for Google App Engine (
camel-gae) have been removed in Fuse 7.0. - Camel jBPM component has been removed in 7.0
-
The Camel jBPM component (
camel-jbpm) has been removed in Fuse 7.0. - Tanuki based wrapper for installing Fuse as a service has been removed in 7.0
-
The Tanuki based wrapper scripts — generated using the
wrapper:installKaraf console command — for installing Fuse as a service have been removed in Fuse 7.0. To install the Apache Karaf container as a service, it is recommended that you use the newkaraf-service-*.shscripts from thebin/contribdirectory instead. - Smooks has been removed in 7.0
- Since Fuse 7.0, the Smooks component for SwitchYard has been removed.
- BPEL has been removed in 7.0
- BPEL (based on the Riftsaw project) has been removed from Fuse 7.0. If you are currently using BPEL, it is recommended that you consider migrating to the Red Hat JBoss BPM Suite.
- Design Time Governance has been removed in 7.0
- The Design Time Governance component has been removed in 7.0.
- Runtime Governance has been removed in 7.0
- Since Fuse 7.0, the Runtime Governance (RTGov) component has been removed.
- S-RAMP has been removed in 7.0
- The SOA Repository Artifact Model and Protocol (S-RAMP) component has been removed in Fuse 7.0.
- bin/patch script has been removed in 7.0
-
The
bin/patchscript (bin\patch.baton Windows O/S) has been removed in a Fuse 7.0. - Spring Dynamic Modules (Spring-DM) is not supported in 7.0
- Spring-DM (which integrates Spring XML with the OSGi service layer in Apache Karaf) is not supported in Fuse 7.0 and you should use the Blueprint framework instead. Using Blueprint XML does not prevent you from using the Java libraries from the Spring framework: the latest version of Spring is compatible with Blueprint.
- Apache OpenJPA is not supported in 7.0
- The Apache OpenJPA implementation of the Java Persistence API (JPA) is not supported in Fuse7.0. It is recommended that you use the Hibernate implementation instead.
5.6. Replaced in Fuse 7.0
The following features were replaced in Fuse 7.0:
- Geronimo transaction manager has been replaced in 7.0
- In Fuse 7.0, the Geronimo transaction manager in the Karaf container has been replaced by Narayana.
- Jetty container has been replaced in 7.0
- In Fuse 7.0, the Jetty container has been replaced by Undertow. Initially, this change applies only to internal use of the Jetty container (for example, in the Karaf container). Other Jetty components might be removed in a future release.
Chapter 6. Unsupported Features in Fuse 7.6
The following features are unsupported in Red Hat Fuse 7.6.
- Apache Karaf EclipseLink feature is unsupported
- The Apache Karaf EclipseLink feature is not supported in Fuse, because this feature depends on JPA 2.2, while the Karaf container for Fuse 7.2 is aligned with JPA 2.1.
- Apache Aries Blueprint Web module is unsupported
- The Apache Aries Blueprint Web module is not supported in Fuse. The presence of an example featuring Blueprint Web in the community edition of Apache Camel (provided as a separate download) does not imply that this feature is supported in Fuse.
- The PHP scripting language is not supported in Apache Camel on Apache Karaf
- The PHP scripting language is not supported in Camel applications on the Apache Karaf container, because there is no OSGi bundle available for PHP. The PHP scripting language is deprecated in Camel applications on the JBoss EAP container and on the Spring Boot container.
- The Python scripting language is not supported in Apache Camel on Apache Karaf
- The Python scripting language is not supported in Camel applications on the Apache Karaf container, because there is no OSGi bundle available for Python. The Python scripting language is deprecated in Camel applications on the JBoss EAP container and on the Spring Boot container.
Chapter 7. Known Issues
The following subsections describe the known issues in version 7.6.
7.1. CVE Security Vulnerabilities
As a middleware integration platform, Fuse can potentially be integrated with a large number of third-party components. It is not always possible to exclude the possibility that some third-party dependencies of Fuse could have security vulnerabilities. This section documents known security vulnerabilities affecting third-party dependencies of Fuse 7.6.
- ENTESB-12489 CVE-2019-9827 - Fuse Console standalone on Amazon Web Services
-
Due to security concerns, you should not deploy a standalone Fuse application to Amazon Web Services (AWS). This restriction applies to all supported standalone environments (Spring Boot 1.x and 2.x, Karaf, and Red Hat JBoss Enterprise Application Platform). If you want to deploy the Fuse Console standalone on AWS, it is highly recommended that you upgrade to Fuse 7.7 or later and disable the Fuse Console’s proxy servlet by setting the
hawtio.disableProxysystem property totrue. - CVE-2017-12629 Solr/Lucene -security bypass to access sensitive data - CVE-2017-12629
Apache Solr is a popular open source search platform that uses the Apache Lucene search engine. If your application uses a combination of Apache Solr with Apache Lucene (for example, when using the Camel Solr component), it could be affected by this security vulnerability. Please consult the linked security advisory for more details of this vulnerability and the mitigation steps to take.
NoteThe Fuse runtime does not use Apache Solr or Apache Lucene directly. The security risk only arises, if you are using Apache Solr and Apache Lucene together in the context of an integration application (for example, when using the Camel Solr component).
- Multiple CVEs Multiple CVEs related to jackson-databind security vulnerability
Applications that that use the FasterXML
jackson-databindlibrary to instantiate Java objects by deserializing JSON content are potentially vulnerable to a remote code execution attack. The vulnerability is not automatic, however, and it can be avoided if you take the appropriate mitigation steps.At a minimum, the following prerequisites must all be satisfied before an attack becomes possible:
You have enabled polymorphic type handling for deserialization of JSON content in
jackson-databind. There are two alternative ways of enabling polymorphic type handling in Jackson JSON:-
Using a combination of the
@JsonTypeInfoand@JsonSubTypesannotations. -
By calling the
ObjectMapper.enableDefaultTyping()method. This option is particularly dangerous, as it effectively enables polymorphic typing globally.
-
Using a combination of the
There are one or more gadget classes in your Java classpath, which have not yet been blacklisted by the current version of
jackson-databind. A gadget class is defined as any class that performs a sensitive (potentially exploitable) operation as a side effect of executing a constructor or a setter method (which are the methods that can be called during a deserialization). The gadget blacklist maintained by the Jackson JSON library is the last line of defence against the remote code execution vulnerability.It is the existence of a large number of gadget classes which explains why there are many individual CVEs related to the
jackson-databindvulnerability. There are different CVEs related to different kinds of gadget class.
If you do need to use the
jackson-databindlibrary in your application, the most important measure you can take to mitigate the risk is this: avoid polymorphic type handling in Jackson JSON and on no account should you call theObjectMapper.enableDefaultTyping()method.
- ENTESB-12539 CVE-2019-10086 commons-beanutils: apache-commons-beanutils: does not suppresses the class property in PropertyUtilsBean by default [fuse-7.4.0]
The Camel Dozer,
camel-dozer, component and the Camel Shiro,camel-shiro, component depend on a version of thecommons-beanutilslibrary that has a CVE security vulnerability. Your application could potentially be affected by this security vulnerability, if you deploy the Camel Dozer or Camel Shiro component in one of the following containers:- Spring Boot 1 container
- Spring Boot 2 container
- JBoss EAP container
For the Spring Boot 1 and Spring Boot 2 container types, you can work around this security vulnerability by customizing the dependencies in your project’s Maven POM file.
For the JBoss EAP container type, no workaround is available at this time and we therefore recommend that you do not use the Camel Dozer or Camel Shiro components with Fuse on EAP. After Fuse 7.6.0 is released, a patch will be made available to fix the
common-beanutilsdependency in Fuse on EAP. Contact Red Hat Support for details of the patch.To work around the dependency issue on Spring Boot 1 and Spring Boot 2, modify the Maven POM file for the application, as follows. For example, given a dependency on the
camel-dozer-starterartifact, like this:<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-dozer-starter</artifactId> </dependency>Modify the preceding dependency, replacing it with the following lines:
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-dozer-starter</artifactId> <exclusions> <exclusion> <groupId>commons-beanutils</groupId> <artifactId>commons-beanutils</artifactId> </exclusion> </exclusions> </dependency> <dependency> <groupId>commons-beanutils</groupId> <artifactId>commons-beanutils</artifactId> <version>1.9.4.redhat-00002</version> </dependency>NoteThe Apache Karaf container is not affected by this issue, because it already uses a secure version of the
commons-beanutilslibrary by default, and Fuse Online is not affected, because it does not use the Camel Dozer or the Camel Shiro component.
7.2. Fuse Online
The Fuse Online distribution has the following known issues:
- ENTESB-13276 OperatorHub overview doesn’t contain information about all addons
- In Fuse 7.6, the OperatorHub overview does not describe all of the add-ons available for the Fuse Online operator. For full details about the available add-ons, see Descriptions of custom resource attributes that configure Fuse Online.
- ENTESB-13272 Jaeger is disabled by default on OperatorHub
- In Fuse 7.6, if you install Fuse Online from OperatorHub, enhanced activity tracking (which depends on Jaeger) is disabled and cannot be re-enabled after installation, because of the related issue, ENTESB-13275. To work around this issue, install Fuse Online using the command-line script, as described in Installing Fuse Online on OCP.
- ENTESB-13275 Missing Jaeger resources after OperatorHub installation
- In Fuse 7.6, it is not possible to enable enhanced activity tracking (which depends on Jaeger) after installing Fuse Online from OperatorHub. To work around this issue, install Fuse Online using the command-line script, as described in Installing Fuse Online on OCP.
- ENTESB-12072 Missing part of first activity records on OCP 4.2. in case the activity contains error
- In Fuse 7.6, if you install Fuse Online from OperatorHub (which causes Fuse Online to revert to an older implementation of activity tracking), there can be missing log records in first activity logged by an integration running on Fuse Online. To work around this issue, install Fuse Online using the command-line script, as described in Installing Fuse Online on OCP.
- ENTESB-11407 [1.7.8] No activities after small load (~80000 messages in 20hours)
- In Fuse 7.6, if you install Fuse Online from OperatorHub (which causes Fuse Online to revert to an older implementation of activity tracking), the activity tracking logic can result in an exceptionally high number of dead tuples in the database used by Fuse Online to track activities. This issue causes a general slowdown in any operation that requires reads from the database, most notably accessing the list of integrations from the UI or refreshing the activities of an integration. To work around this issue, install Fuse Online using the command-line script, as described in Installing Fuse Online on OCP.
- ENTESB-12854 Fuse online scripts break with space in path
-
In Fuse 7.6, the
install_ocp.shscript does not work with filesystem paths that have spaces in them. Ensure that the Fuse Online install directory does not have any spaces in its path. - ENTESB-12923 Sometimes some of the pods do not come up after upgrade
- In Fuse 7.6, after upgrading, it can happen that some of the Kubernetes pods are not restarted automatically. If this happens, restart the pods manually instead.
- ENTESB-13074 Upgrade db fails with sampledb integration active
- In Fuse 7.6, the upgrade procedure fails, if an integration using the sampleDB is currently active. To work around this problem, stop the integration before performing the upgrade procedure.
- ENTESB-13110 Postgres version check runs on each reconcile even without upgrade
In Fuse 7.6, the Postgres version check is performed during a fresh install, although it is only required during an upgrade. This causes spurious error messages in the log, like the following, which can be safely ignored:
{"level":"error","ts":1583164580.847065,"logger":"configuration","msg":"Unable to determine current version of PostgreSQL running in syndesis-db pod","error":"dial tcp: lookup syndesis-db on 10.0.145.81:53: no such host"- ENTESB-12175 Camel-k integrations stay deployed even when deleted in UI
-
In Fuse 7.5, if Camel K is enabled and you delete an integration in the UI, the Camel K integration continues to run, but isn’t displayed in Fuse Online. To work around this issue, first stop the integration in the UI and then delete it with the
kamel deletecommand. - ENTESB-12174 API Provider running on camel-k has empty parameters
- In Fuse 7.5, if Camel K is enabled and you create an API Provider action that uses query parameters, the parameters are empty.
- ENTESB-12181 Operator tries to update outdated Syndesis resource
When installing Fuse Online using the operator, the following error occurs multiple times, but it can be ignored as it has no significant effect on the installation:
{"level":"error","ts":1558617960.2453232,"logger":"controller","msg":"Error reconciling","action":"*action.startupAction","phase":"Starting","error":"Operation cannot be fulfilled on syndesises.syndesis.io \"app\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/syndesisio/syndesis/install/operator/vendor/github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/src/github.com/syndesisio/syndesis/install/operator/vendor/github.com/go-logr/zapr/zapr.go:128\ngithub.com/syndesisio/syndesis/install/operator/pkg/controller/syndesis.(*ReconcileSyndesis).Reconcile\n\t/go/src/github.com/syndesisio/syndesis/install/operator/pkg/controller/syndesis/syndesis_controller.go:120\ngithub.com/syndesisio/syndesis/install/operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/src/github.com/syndesisio/syndesis/install/operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:215\ngithub.com/syndesisio/syndesis/install/operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func1\n\t/go/src/github.com/syndesisio/syndesis/install/operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:158\ngithub.com/syndesisio/syndesis/install/operator/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1\n\t/go/src/github.com/syndesisio/syndesis/install/operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133\ngithub.com/syndesisio/syndesis/install/operator/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil\n\t/go/src/github.com/syndesisio/syndesis/install/operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:134\ngithub.com/syndesisio/syndesis/install/operator/vendor/k8s.io/apimachinery/pkg/util/wait.Until\n\t/go/src/github.com/syndesisio/syndesis/install/operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88"}- ENTESB-10577 Apicurito does not support YAML Open API spec files
- In Fuse 7.4 on OpenShift, Apicurito generates OpenAPI specification files in YAML format by default, but is not capable of re-importing the generated YAML file. Only JSON format can be imported into Apicurito at the moment.
7.3. Fuse on OpenShift
This section lists issues that affect the deployment of Fuse applications on OpenShift. For details of issues affecting specific containers, see also the sections for Spring Boot, Fuse on Apache Karaf, and Fuse on JBoss EAP. The Fuse on OpenShift distribution has the following known issues:
- ENTESB-13867 Quickstarts fails on Openshift 4.4
-
In Fuse 7.6.0 on OpenShift Container Platform (OCP) 4.4, the quickstarts for Fuse on OpenShift fail to deploy, because the deployment YAML files are using an older version of the deployment API that is incompatible with OpenShift 4.4. This is happening because OpenShift 4.4 has been upgraded to Kubernetes 1.17, which no longer accepts the older version of the deployment API (that is,
extensions/v1beta1) and requires deployment API versionapps/v1instead (which is documented in Deployment v1 apps). - ENTESB-12224 Fuse console - Select a container dropdown vague behaviour
- In Fuse 7.5.0 on OCP 4 and on OCP 3, after connecting to an application through the Fuse Console, the Select a container dropdown menu behaves unreliably, sometimes showing other deployed Fuse containers and sometimes not.
- ENTESB-12238 [SB2] Quickstarts arquillian test fail
In Fuse 7.5.0, some of the Spring Boot 2 quickstarts (generated either from Maven archetypes or quickstart templates) fail to build and deploy to OpenShift. The following Spring Boot 2 Maven archetypes are affected:
-
spring-boot-camel-archetype -
spring-boot-camel-infinspan-archetype -
spring-boot-cxf-jaxrs-archetype -
spring-boot-cxf-jaxws-archetype
And the following Spring Boot 2 templates:
-
spring-boot-2-camel-template -
spring-boot-2-camel-infinspan-template -
spring-boot-2-cxf-jaxrs-template -
spring-boot-2-cxf-jaxws-template
To work around this issue, after generating a Maven project for one of these quickstarts, edit the project’s Maven
pom.xmlfile to add the following dependency:<dependency> <groupId>org.assertj</groupId> <artifactId>assertj-core</artifactId> <version>2.4.1</version> <scope>test</scope> </dependency>
-
- ENTESB-10577 Apicurito does not support YAML Open API spec files
- In Fuse 7.4 on OpenShift, Apicurito generates OpenAPI specification files in YAML format by default, but is not capable of re-importing the generated YAML file. Only JSON format can be imported into Apicurito at the moment.
7.4. Fuse on Spring Boot
Fuse on Spring Boot has the following known issues:
- ENTESB-12539 CVE-2019-10086 commons-beanutils: apache-commons-beanutils: does not suppresses the class property in PropertyUtilsBean by default [fuse-7.4.0]
-
In Fuse 7.6, the Camel Dozer,
camel-dozer, component and the Camel Shiro,camel-shiro, component depend on a version of thecommons-beanutilslibrary that has a CVE security vulnerability. Your application could potentially be affected by this security vulnerability, if you deploy the Camel Dozer or Camel Shiro component in a Spring Boot 1 container, a Spring Boot 2 container, or a JBoss EAP container. You can fix this security vulnerability by customizing the dependencies in your project’s Maven POM file — for details, see CVE for ENTESB-12539. - ENTESB-13210 Different version of artemis-jms-client on SB2, SB1, Karaf
-
In Fuse 7.6, the version of
artemis-jms-clientfor the Spring Boot 2 container (2.11.0.redhat-00005) is different from the version ofartemis-jms-clientfor the Spring Boot 2 container and the Apache Karaf container (2.11.0.redhat-00004). Both of these client versions are compatible with AMQ Broker 7.6, so this difference can be safely ignored. - ENTESB-13211 Unproductised version of Hawtio in Spring Boot 2 Bom
In Fuse 7.6, the Spring Boot 2 bill of materials (BOM) file references an unproductised version of Fuse Console (Hawtio). To work around this problem, in the Maven POM file for your Spring Boot 2 project, add the following lines to the dependency management section of the POM:
<dependencyManagement> <dependency> <groupId>io.hawt</groupId> <artifactId>hawtio-springboot</artifactId> <version>2.0.0.fuse-sb2-760022-redhat-00001</version> </dependency> </dependencyManagement>
7.5. Fuse on Apache Karaf
Fuse on Apache Karaf has the following known issues:
- ENTESB-11189 Fuse Camel elasticsearch-rest component - ClassNotFoundException and IllegalAccessError
-
In Fuse 7.6, the
camel-elasticsearch-restcomponent does not work in the Apache Karaf container, because the corresponding feature is not correctly packaged. - ENTESB-13135 Automatic encryption of users2.properties on windows makes you unable to login
-
In Fuse 7.6, if you enable Jasypt encryption for
etc/users2.propertieson Windows, it becomes impossible to login, even with the correct credentials. - ENTESB-8140 Start level of hot deploy bundles is 80 by default
In the Fuse 7.0 GA release, in the Apache Karaf container the start level of hot deployed bundles is 80 by default. This can cause problems for the hot deployed bundles, because there are many system bundles and features that have the same start level. To work around this problem and ensure that hot deployed bundles start reliably, edit the
etc/org.apache.felix.fileinstall-deploy.cfgfile and change thefelix.fileinstall.start.levelsetting as follows:felix.fileinstall.start.level = 90
- ENTESB-7664 Installing framework-security feature kills karaf
The
framework-securityOSGi feature must be installed using the--no-auto-refreshoption, otherwise this feature will shut down the Apache Karaf container. For example:feature:install -v --no-auto-refresh framework-security
7.6. Fuse on JBoss EAP
Fuse on JBoss EAP has the following known issues:
- ENTESB-12539 CVE-2019-10086 commons-beanutils: apache-commons-beanutils: does not suppresses the class property in PropertyUtilsBean by default [fuse-7.4.0]
-
In Fuse 7.6, the Camel Dozer,
camel-dozer, component and the Camel Shiro component depend on a version of thecommons-beanutilslibrary that has a CVE security vulnerability. Your application could potentially be affected by this security vulnerability, if you deploy the Camel Dozer or Camel Shiro component in a Spring Boot 1 container, a Spring Boot 2 container, or a JBoss EAP container. For the JBoss EAP container type, no workaround is available at this time and we therefore recommend that you do not use the Camel Dozer or Camel Shiro components with Fuse on EAP. After Fuse 7.6.0 is released, a patch will be made available to fix thecommon-beanutilsdependency in Fuse on EAP. See CVE for ENTESB-12539. - ENTESB-13168 Camel deployment on EAP domain mode is not working on Windows
- In Fuse 7.6.0, for Fuse on JBoss EAP, the Camel subsystem cannot be deployed on JBoss EAP in domain mode on Windows OS.
7.7. Apache Camel
Apache Camel has the following known issues:
- ENTESB-11060 [camel-linkedin] V1 API is no longer supported
- Since Fuse 7.4.0, the Camel LinkedIn component is no longer able to communicate with the LinkedIn server, because it is implemented using the LinkedIn Version 1.0 API, which is no longer supported by LinkedIn. The Camel LinkedIn component will be updated to use the Version 2 API in a future release of Fuse.
- ENTESB-7469 Camel Docker component cannot use Unix socket connections on EAP
-
Since Fuse 7.0, the
camel-dockercomponent can connect to Docker only through its REST API, not through UNIX sockets. - ENTESB-5231 PHP script language does not work
- The PHP scripting language is not supported in Camel applications on the Apache Karaf container, because there is no OSGi bundle available for PHP.
- ENTESB-5232 Python language does not work
- The Python scripting language is not supported in Camel applications on the Apache Karaf container, because there is no OSGi bundle available for Python.
- ENTESB-2443 Google Mail API - Sending of messages and drafts is not synchronous
- When you send a message or draft, the response contains a Message object with an ID. It may not be possible to immediately get this message via another call to the API. You may have to wait and retry the call.
- ENTESB-2332 Google Drive API JSON response for changes returns bad count of items for the first page
-
Google Drive API JSON response for changes returns bad count of items for the first page. Setting
maxResultsfor a list operation may not return all the results in the first page. You may have to go through several pages to get the complete list (that is by settingpageTokenon new requests).
Chapter 8. Fixed Issues in Fuse 7.6
The following sections list the issues that have been fixed in Fuse 7.6:
8.1. Enhancements in Fuse 7.6
The following table lists the enhancements in Fuse 7.6.
| Issue | Description |
|---|---|
| Refactor org.apache.camel.processor.aggregate.jdbc.JdbcAggregationRepository to make it easy to extend | |
| Reinstate maven archetypes for SB2 | |
| Update to productised Jaeger | |
| Upgrade operator-sdk for syndesis operator | |
| Backport CAMEL-14307 - allow empty routing key when declaring RabbitMQ dead letter exchange | |
| Backport CAMEL-14292: Remove unwanted dependency to google-http-client library | |
| Backport CAMEL-13841 - Pulsar: Add the ability to manually acknowledge a message consumed from Pulsar | |
| Remove useless option form camel-box Readme | |
| Fuse Online: unable to configure syntesis-db pvc type | |
| Add Karaf feature definition for camel-as2 component | |
| "Backport CAMEL-14184 - Allow setting Pulsar Message headers (properties | |
| Camel exec component’s option to mask argument values in log | |
| Update operator metrics endpoint to include version information | |
| Add an option to the installation script to supply a custom CR at install time | |
| Consolidate operator configuration options (CRD) | |
| Move to Camel 2.23 | |
| Runtime nested collection support | |
| APICurito operator should have a default operand version | |
| Camel-Pulsar: Increase the configuration options | |
| Backport CAMEL-14047 | |
| "Nomenclature around ""Import Data Source"" in DV" | |
| Edit API provider edit flow - edit button would be much more useful | |
| Syndesis DB connector - raise error when trying to insert duplicate ID | |
| [Conditional Flow] moving a condition changes layout based on help message under it | |
|
Verify the | |
| Fuse 7: Requirement for CXF-WS(soap webservice) springboot quickstart with spring XML based configuration. | |
| 'Set Values' Step That Just Fills In The Values Needed According To The Subsequent Data Shape | |
| Provide a config option to replace Jaeger in-memory with external Jaeger backend | |
| Align to latest AMQ Streams (kafka-clients-2.4.0.redhat-00005) |
8.2. Feature requests in Fuse 7.6
The following table lists the features requests in Fuse 7.6.
| Issue | Description |
|---|---|
| Fuse 7 (On OpenShift) logging support for ElasticSearch | |
| Import/Export of Virtualization | |
| provide configuration for customization of login page text (banner) | |
| Collection Support for Conditional Mapping - 7.6 | |
| Extend upgrade/backup/restore to cover an external database | |
| UX: Make editing a more obvious choice in the Integration list | |
| Automate regression test coverage for 18 Fuse customer issues | |
| Move to jaeger based activity tracking | |
| Support versioning of the Virtualization | |
| Operator Backup and Restore | |
| Apicurio Undo doesn’t Undo in Syndesis and leaves you in a deadend state | |
| Autodiscovery of AMQ Streams | |
| Support OpenAPI 3.0 | |
| """initialsize"" option for narayana connection pool like the one for org.apache.commons.dbcp2.BasicDataSource" | |
| [operator] external database connection string option in syndesis custom resource | |
| Suppress extension when Camel K is used in Syndesis | |
| [Syndesis] MongoDB connector - GA features | |
| Update org.apache.commons/commons-text version | |
| Request to support Fuse 7 on EAP domain mode | |
| Validate that the Red Hat font changes don’t break the UI | |
| Validate that the dark background is working correctly | |
| Camel-Pulsar component support on Fuse 7.x |
8.3. Bugs resolved in Fuse 7.6
The following table lists the resolved bugs in Fuse 7.6.
| Issue | Description |
|---|---|
| pax-jdbc-db2: No setter in class com.ibm.db2.jcc.DB2SimpleDataSource for property url | |
| [camel-as2] Integration tests are not working | |
| [Hawtio] It is possible to create an endpoint with name made up of most special signs | |
| spring-boot-cxf-jaxrs vs spring-boot-cxf-jaxrs-xml | |
| DB backups are created by incorrect postgres version | |
| Remove FuseK operator from operatorhub | |
| Dynamo DB connector can’t insert and delete records | |
| Operatorhub manifest file contained in the Fuse Online CR1 operator references 7.5.0. | |
| prometheus doesn’t work with OCP 4.4 | |
| Provide a default custom-resource.yml (file) to fuse-online-install | |
| The build of the integration with MongoDB fails | |
| Invalid date and time for steps in the activity log with Jaeger addon | |
| [7.6.CR1] Wrong postgresql image used by syndesis operator | |
| netty-all dependency not available | |
| Custom API Client - API key doesn’t use the key’s name | |
| Install cluster doesnt install additional stuff when the CRD is present | |
| AWS S3 component copy operation doesn’t work | |
| Apicurito ER1 operator image has 7.5.0 version everywhere | |
| Fix new Red Hat font misalignment | |
| AWS dynamo Db - unable to insert multiple records using integration | |
| Allow users to supply syndesis CR to install_ocp script | |
| OpenAPI 3.x not supported issues are ignored without warning | |
| Old version of Atlasmap in Fuse Online ER1 | |
| Servers field cannot be used in OpenAPi specification | |
| ClassNotFoundException in the integration with Mongo connection | |
| Maven Central now requires HTTPS | |
| Update release number in links from Fuse Online console to customer portal | |
| Camel: Master component URI with RAW() let parameter value to be partially encoded | |
| Blank screen when user edits a step extension with no propertyDefinitionSteps | |
| [SB2] spring-boot-camel quickstart using different camel version | |
| Google Calendar time → GC time data mapping throws 'Invalid date/time format: …' | |
| [SB1] and [SB2] quickstart spring-boot-camel-xa is not productized | |
| Upgrade cant get jobs.batch when using non-admin user | |
| """Extensions"" page is still displayed when using Camel K" | |
| [SB2] spring-boot-cxf-jaxws is using different version of fabric8 | |
| Collection on last level of XML document in Atlasmap identified as an object instead of collection | |
| Check of the integration state via Public API endpoint causes Internal Server Exception | |
| The order of steps in the activity log is not in order in which the steps are defined. | |
| Collection on 2nd level of XML document in Atlasmap can’t be mapped to same level in different types (json/java) collections | |
| Unable to set memory limits for syndesis components in CR | |
| API client description metiones only OpenAPI 2.o | |
| application-templates are using non-productized eap quickstarts | |
| Apicurito ER1 image contains older version than upstream | |
| Camel BOMs missing camel-rest-openapi | |
| Graceful shutdown doesn’t work with Karaf camel undertow | |
| Inconsistent naming for Amazon DynamoDB connector | |
| Syndesis step extension fails when included in an integration with an API endpoint | |
| Selecting PV for DB with labels doesn’t work | |
| Camel Jetty/Http4 producers should respect Content-Length/Transfer-Encoding:Chunked headers | |
| Thread leak in camel-jetty component if maxThreads or minThreads property is set | |
| Remove image stream for database | |
| Backport CAMEL-14194 - Invalid JID is generated for private chat in XMPP component | |
| Remove AMQ broker from productized bits | |
| Backport CAMEL-14129 | |
| Backport CAMEL-14143 | |
| Integration metrics don’t work | |
| The time of assembling increases linearly according to the integration name | |
| [Operator] Some configuration cant be changed from its default value | |
| "Camel Undertow does not provide an option to use the producer as the ""Host"" header when bridging two http endpoints" | |
| Missing image stream for Public Oauth proxy | |
| Verify Documentation is Live - findings | |
| "Camel-dozer error shown on Fuse | |
| An integration pod with a gmail oauth connection is not able to start | |
| UI doesn’t show a Google Calendar step | |
| Divergence in camel-aws-sqs component | |
| Unable to deploy with Camel-K | |
| Daily build is using latest images | |
| Integration uptime doesn’t contain any data | |
| XPath evaluation fails with null body using Saxon-HE-9.8.0-8_1 | |
| Problem with Olingo2 and authenticated metadata | |
| API Provider methods display regression | |
| pax-web could not parse envEntryType Element in hawtio-war/WEB-INF/web.xml | |
| Camel file’s tempPrefix does not work correctly if the target is Windows UNC path | |
| Mongo Consumer form has undefined tooltips | |
| Camel defines invalid version of okhttp for pubnub and influxdb | |
| bin/contrib/karaf-service.sh does not work until executed from bin/contrib folder | |
| Import process should include Return Codes | |
| credentials of a connector attached to a connection are plain text | |
| Click to refresh doesn’t refresh and leads to black screen + product logo | |
| [karaf-maven-plugin] client goal + script execution not working correctly | |
| Fuse Online: Data Mapper to REST call: ignore collection parameter | |
| NullPointerException when saving an oauth connection description | |
| Usage of Middle steps as the Final step | |
| ServiceVdbGenerator has problem if view does not end in semicolon | |
| Unable to put/query/remove records into and from DynamoDb | |
| [Operator] ImageStreamNamespace doesn’t provide much value | |
| Unable to activate Knative connector | |
| NoSuchMethodError okhttp3.HttpUrl.get(String) | |
| Conditional Flows - breadcrumbs - select flow: Make it scrollable | |
| AWS dynamo Db - query action output with Atlasmap - AtlasException: Errors: [Cannot read a field '/email' of JSON document | |
| Google sheets are unreachable for Validation | |
| AWS dynamoDB - add unique icon for the new connector | |
| "Non-unique connection name - ""Bad request"" error message" | |
| Incorrect font type and styling for definition list on multiple pages | |
| The AWS dynamoDB no update or error response when trying to insert item with same ID | |
| React Error on Syndesis customisation | |
| No warning when creating integration with non-unique name | |
| Dropbox upload mode looks initialized in the UI but isn’t | |
| Increase the default time on SQL queries | |
| [Connections] Invalid credentials lead to Something is wrong page | |
| [OAuth] Twitter connector validation unreadable error message | |
| [Upgrade] Rebuilding integration after upgrade results in Failure executing: PATCH | |
| Box - no property for fileName in upload action | |
| [Upgrade] Operator throws errors in log related to upgrade pvc | |
| "Validate reconnecting Twitter OAuth connection shows ""Could not authenticate you.""" | |
| No confirmation dialog shows up when leaving the integration | |
| [Rollback] syndesis-db-metrics causes db rollback to fail | |
| API client connectors don’t use edited specification | |
| Unable to recreate integration with the same name on OCP 3.11 | |
| Backport CAMEL-14267: Fix a nullPointerException in convertIfRequired | |
| Backport CAMEL-14224: Fix camel-websocket sendToAll to be faster | |
| Edits to DV strings in data-translations.en.json to comply with style guidelines | |
| fuse-online-install delete project after creating secret with credentials | |
| The activity log doesn’t show error step | |
| Unable to validate box | |
| Unable to validate anything with AWS | |
| DV Addon uses non-existing image | |
| Unable to specify external DB for syndesis | |
| Error message on deploying war with spring-ws-core on Fuse over EAP | |
| Unable to use stored procedures | |
| Webhook step in activity log causes NPE on the server when Jaeger addon is enabled | |
| Back-off pulling image of Camel-K runtime (TP) | |
| Unable to upgrade from 1.8 to 1.9.100-20191202 because of change in syndesis CR | |
| API Provider specification ignores data type in reponses | |
| API Provider finish integration step can be replaced | |
| "Route irc→irc cycles the message because of ""irc.target"" header" | |
| Todo buildconfig breaks upgrade process | |
|
Operator subcommand | |
| Upgrade tries to upgrade postgres even if the version is the same | |
| Sort out upgrade cases related to postgres | |
| Operator doesn’t react on changes in Syndesis CR | |
| Cannot install Fuse Online | |
| Fuse On OpenShift eap quickstarts are using non-ga repositories | |
| Regular user cant patch syndesis object | |
| Build of S2I quickstart on OCP 4.2 fails with OOMKilled | |
| spring-boot-camel-amq-archetype missing arquillian integration steps on README.adoc | |
| Fuse Online install scripts reference old operator image tag | |
| [7.6.CR1] Todo pod does not deploy on OCP 4.4 | |
| spring-boot-camel-amq quickstart doesn’t work | |
| Enable the jaeger addon by default in fuse-online-install | |
| S2I Quickstarts contain wrong BOM |
