Chapter 1. Red Hat build of Apache Camel for Spring Boot 4.4 release notes
1.1. Features in Red Hat build of Apache Camel for Spring Boot
Red Hat build of Apache Camel for Spring Boot introduces Camel support for Spring Boot which provides auto-configuration of Camel, and starters for many Camel components. The opinionated auto-configuration of the Camel context auto-detects Camel routes available in the Spring context and registers key Camel utilities (like producer template, consumer template and the type converter) as beans.
1.2. Supported platforms, configurations, databases, and extensions for Red Hat build of Apache Camel for Spring Boot
- For information about supported platforms, configurations, and databases in Red Hat build of Apache Camel for Spring Boot, see the Supported Configuration page on the Customer Portal (login required).
- For a list of Red Hat Red Hat build of Apache Camel for Spring Boot extensions, see the Red Hat build of Apache Camel for Spring Boot Reference (login required).
1.3. The javax to jakarta Package Namespace Change
The Java EE move to the Eclipse Foundation and the establishment of Jakarta EE, since Jakarta EE 9, packages used for all EE APIs have changed to jakarta.*
Code snippets in documentation have been updated to use the jakarta.* namespace, but you of course need to take care and review your own applications.
This change does not affect javax packages that are part of Java SE.
When migrating applications to EE 10, you need to:
-
Update any import statements or other source code uses of EE API classes from the
javaxpackage tojakarta. -
Change any EE-specified system properties or other configuration properties whose names begin with
javax.to begin withjakarta.. -
Use the
META-INF/services/jakarta.[rest_of_name]name format to identify implementation classes in your applications that use the implement EE interfaces or abstract classes bootstrapped with thejava.util.ServiceLoadermechanism.
1.3.1. Migration tools
- Source code migration: How to use Red Hat Migration Toolkit for Auto-Migration of an Application to the Jakarta EE 10 Namespace
- Bytecode transforms: For cases where source code migration is not an option, the open source Eclipse Transformer
Additional resources
- Background: Update on Jakarta EE Rights to Java Trademarks
- Red Hat Customer Portal: Red Hat JBoss EAP Application Migration from Jakarta EE 8 to EE 10
- Jakarta EE: Javax to Jakarta Namespace Ecosystem Progress
1.4. Important notes for Red Hat build of Apache Camel for Spring Boot
1.4.1. Support for IBM Power and IBM Z
Red Hat build of Camel Spring Boot is now supported on IBM Power and IBM Z.
1.4.2. Support for EIP circuit breaker
The Circuit Breaker EIP for Camel Spring Boot supports Resilience4j configuration. This configuration provides integration with Resilience4j to be used as Circuit Breaker in Camel routes.
1.4.3. Support for Stateful transactions
The Red Hat build of Camel Example Spring Boot provides a Camel Spring Boot JTA quickstart. This quickstart demonstrates how to run a Camel Service on Spring Boot that supports JTA transactions on two external transactional resources: a database (MySQL) and a message broker (Artemis). These external resources are provided by OpenShift which must be started before running this quickstart.
1.5. Fixed issues for Red Hat build of Apache Camel for Spring Boot
The following sections list the issues that have been fixed in Red Hat build of Apache Camel for Spring Boot.
1.5.1. Red Hat build of Apache Camel for Spring Boot version 4.4 Enhancements
| Issue | Description |
|---|---|
| Support Hawtio console for Camel for Spring Boot | |
| camel-olingo4 support | |
| Adding a Kafka Batch Consumer | |
| [RFE] Support component camel-smb | |
| Enhancing XML IO DSL to support beans like in YAML DSL | |
| Camel for Spring Boot support for IBM Z/P | |
| Provide support to configure algorithm for camel-ssh component | |
| Add support for camel-flink | |
| Add Azure SAS support for azure blob storage | |
| Create and support a new Camel CICS component | |
| Support component camel-splunk | |
| Offline Maven Builder Script | |
| Support component camel-jasypt | |
| Support component camel-kudu | |
| Support cxf-integration-tracing-opentelemetry | |
| Support component camel-groovy | |
| BeanIO support | |
| camel-cics - support connectivity via channels |
1.5.2. Red Hat build of Apache Camel for Spring Boot version 4.4 fixed issues
| Issue | Description |
|---|---|
| CVE-2023-35116 jackson-databind: denial of service via cylic dependencies | |
| CVE-2023-2976 guava: insecure temporary directory creation | |
| AWS SQS component, OCP probes cause POD error | |
| [Micrometer Observability] Unable to see trace id and span id in MDC | |
| Please provide examples that show Camel AMQP/JMS used with a connection pool | |
| CVE-2023-5632 mosquitto: Possible Denial of Service due to excessive CPE consumption | |
| [camel-mail] java.lang.ClassNotFoundException: org.eclipse.angus.mail.imap.IMAPStore | |
| Dependency convergence error for org.ow2.asm:asm when using CXF and JSON Path | |
| Dependency convergence error for org.bouncycastle:bcprov-jdk18on:jar:1.72 | |
| Add support for findAndModify Operation | |
| CVE-2023-51074 json-path: stack-based buffer overflow in Criteria.parse method | |
| Support cxf-integration-tracing-opentelemetry | |
| CVE-2024-21733 tomcat: Leaking of unrelated request bodies in default error page | |
| camel-bean - Allow to configure bean introspection cache on component | |
| Dependency convergence errors when using cxf-rt-rs-service-description-openapi-v3:4.0.2.fuse-redhat-00046 and camel-openapi-java-starter:4.0.0.redhat-00039 | |
| CVE-2023-45860 Hazelcast: Permission checking in CSV File Source connector | |
| AMQP publisher application is losing messages with local JMS transaction enabled | |
| CVE-2024-26308 commons-compress: OutOfMemoryError unpacking broken Pack200 file | |
| commons-compress: Denial of service caused by an infinite loop for a corrupted DUMP file [rhint-camel-spring-boot-4] | |
| restConfiguration section is ignored when using XML DSL IO | |
| Issue while marshalling/ummarshalling XML to JSON. | |
| CVE-2023-5685 xnio: StackOverflowException when the chain of notifier states becomes problematically big | |
| onException handler does not set content in the body response when used with servlet/platform-http | |
| [Camel-sap] Unable to connect to SAP server through CSB configuration properties | |
| camel-file - Can ant filter be optimized when using min/max depth with orphan marker file check | |
| NPE occurs If user uses OpenTelemetryTracingStrategy and opentelemetry.exclude-patterns to exclude "direct*" | |
| OpenTelemetryTracingStrategy separates a trace into 2 branches with opentelemetry.exclude-patterns "process*" or "bean*" | |
| Request to offer connection pooling in camel-cics | |
| Put a max default configurable limit on the Jose P2C parameter & Only explicitly return the stylesheet in WadlGenerator and not other URLs | |
| Type Conversion Error from byte[] to Long in Camel 4 from Kafka Topic for JMS* headers | |
| camel-salesforce - startup error | |
| CVE-2024-22262 springframework: URL Parsing with Host Validation |
1.6. Known issues for Red Hat build of Apache Camel for Spring Boot
The following sections list known issues for Red Hat build of Apache Camel for Spring Boot.
1.6.1. Red Hat build of Apache Camel for Spring Boot version 4.4 known issues
- CSB-4318 Fail to deploy on OCP using Openshift Maven Plugin if spring.boot.actuator.autoconfigure is not in the dependencies
Jkube maven plugin uses the following condition to check if the application exposes health endpoint (using
SpringBootHealthCheckEnricher). Both classes are in the classpath:-
org.springframework.boot.actuate.health.HealthIndicator -
org.springframework.web.context.support.GenericWebApplicationContext
-
However, the /actuator/health wil be not exposed without the configuration of the actuator. This creates discordance between the readiness/liveness probes configured by JKube (they both uses the above endpoint) and what the application is exposing.
This misconfiguration causes a failing deployment config on OpenShift Container Platform since the generated pod will never be in Ready status since the probe`s call for an endpoint is not configured. So in order to make the application work on OpenShift Container Platform, which is deployed using JKube (openshift-maven-plugin), it is necessary to have both web and actuator autoconfiguration in the dependencies.
Following example shows how to configure web and actuator autoconfiguration.
Example
<dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-web</artifactId> </dependency> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-actuator</artifactId> </dependency>
Update the archetype as shown below. The applications built from the following archetype will be deployed correctly using JKube.
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-web</artifactId>
<exclusions>
<exclusion>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-tomcat</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-undertow</artifactId>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-actuator</artifactId>
</dependency>This issue affects the custom applications with missing one of the above dependencies.
