Release Notes for Red Hat build of Apache Camel Extensions for Quarkus 2.13

Red Hat build of Apache Camel Extensions for Quarkus 2.13

What's new in Red Hat build of Apache Camel Extensions for Quarkus

Red Hat build of Apache Camel Extensions for Quarkus Documentation Team

Abstract

Describes the Red Hat build of Apache Camel Extensions for Quarkus product and provides the latest details on what's new in this release.

Chapter 1. Camel Extensions for Quarkus 2.13.3 release notes

1.1. Camel Extensions for Quarkus features

Fast startup and low RSS memory
Using the optimized build-time and ahead-of-time (AOT) compilation features of Quarkus, your Camel application can be pre-configured at build time resulting in fast startup times.
Application generator
Use the Quarkus application generator to bootstrap your application and discover its extension ecosystem.
Highly configurable

All the important aspects of a Camel Extensions for Quarkus application can be set up programmatically with CDI (Contexts and Dependency Injection) or by using configuration properties. By default, a CamelContext is configured and automatically started for you.

Check out the Configuring your Quarkus applications guide for more information on the different ways to bootstrap and configure an application.

Integrates with existing Quarkus extensions
Camel Extensions for Quarkus provides extensions for libraries and frameworks that are used by some Camel components which inherit native support and configuration options.

1.2. Supported platforms, configurations, databases, and extensions

  • For information about supported platforms, configurations, and databases in Camel Extensions for Quarkus version 2.13.2, see the Supported Configuration page on the Customer Portal (login required).
  • For a list of Red Hat Camel Extensions for Quarkus extensions and the Red Hat support level for each extension, see the Extensions Overview chapter of the Camel Extensions for Quarkus Reference (login required).

1.3. BOM files for Camel Extensions for Quarkus

  • To configure your Red Hat Camel Extensions for Quarkus version 2.13.3 projects to use the supported extensions, use the latest Bill Of Materials (BOM) version 2.13.7.SP3-redhat-00003 or newer, from the Redhat Maven Repository.

For more information about BOM dependency management, see Developing Applications with Camel Extensions for Quarkus

1.4. Technology preview extensions

Items designated as Technology Preview in the Extensions Overview chapter of the Camel Extensions for Quarkus Reference have limited supportability, as defined by the Technology Preview Features Support Scope.

Note

Although CXF is fully supported, issues remain with this release of Camel Extensions for Quarkus. The following features are still in Technology Preview:

CEQ-5390 WS-ReliableMessaging
Full support for CXF WS-ReliableMessaging is currently unavailable, and it remains in Technology Preview for 2.13.3.

1.5. Known issues

CEQ-6263 OpenTelemetry traces not being generated in sequence

If you try to capture DB call traces through OpenTelemetry, the bean call executes in a new thread, and a new OpenTelemetry Context is created in the JBDC driver, with a new span outside the expected parent.

Note

To ensure that the sequence of recorded spans is correct, you must use the full to("bean:") endpoint URI and not the shortened .bean() EIP DSL method.

CEQ-6217 Templated route fails if it is processed before route template
If the templated route definition is set in camel.main.routes-include-pattern before the route template definition, the Camel application will fail to start.
CEQ-6203 CXF on OpenShift requires quarkus.cxf.path property

When you deploy Camel Quarkus with CXF on OpenShift, you must set the quarkus.cxf.path property.

Otherwise, the pod will not work due to missing liveness/readiness probes:

Example

11:36:07,343 Can't find the request for http://10.10.10.10:8080/q/health/ready's Observer

CEQ-5705 Extension camel-quarkus-snmp not supported in Native

In Camel Extensions for Quarkus we support the camel-quarkus-snmp component in JVM mode only.

SNMP version 3 is supported only for the operation poll. (This limitation is caused by an issue in Camel 3.18.6. For more information, see CAMEL-19298).

Note

Currently, http://code.quarkus.redhat.com may not list camel-quarkus-snmp, but we do in fact support the component in JVM mode.

1.6. Important notes

Support for AdoptiumJDK
Camel Extensions for Quarkus version 2.13.3 includes support for AdoptiumJDK 11 and AdoptiumJDK 17.
Camel upgraded from version 3.14.2 to version 3.18.6

Camel Extensions for Quarkus version 2.13.3 has been upgraded from Camel version 3.14.2 to Camel version 3.18.6. For additional information about each intervening Camel patch release, refer to the following:

Camel Quarkus upgraded from version 2.7 to version 2.13

Camel Extensions for Quarkus version 2.13.3 has been upgraded from Camel Quarkus version 2.7 to Camel Quarkus version 2.13. For additional information about each intervening Camel Quarkus patch release, refer to the following:

1.7. Resolved issues

The following table lists known issues that were affecting Camel Extensions for Quarkus, which have been fixed in Camel Extensions for Quarkus version 2.13.3.

Table 1.1. Resolved issues

IssueDescription

CEQ-6263

OpenTelemetry traces not being generated in sequence.

CEQ-6254

Support extension: camel-quarkus-vertx-http

CEQ-5705

Support extension: camel-quarkus-snmp

CEQ-5265

Support extension: camel-quarkus-yaml-dsl

CEQ-4706

Support extension: camel-quarkus-amqp

CEQ-4618

Support extension: camel-quarkus-jdbc

CEQ-2320

XML DSL Language - extension camel-quarkus-xml-io-dsl

1.7.1. Previous releases

For details of issues resolved between Camel Quarkus 2.7 and Camel Quarkus 2.13, see the Release Notes for each patch release.

1.8. Deprecated Camel Extensions for Quarkus features

The following capabilities and certifications not available in the next major release of CEQ 3.x, and are deprecated in this release.

1.8.1. JDK 11

Deprecated features

JDK 11 is deprecated in this release of Camel Extensions for Quarkus. It is not supported in future releases.

1.8.2. Camel-microprofile-metrics

Camel-microprofile-metrics is deprecated since Camel Extensions for Quarkus version 2.13.2. Use the camel-micrometer instead.

1.9. Extensions added in this release

The following table lists the extensions added in this release of Camel Extensions for Quarkus version Camel Extensions for Quarkus .

Table 1.2. Added extensions

ExtensionArtifactDescriptionNote

AMQP

camel-quarkus-amqp

Messaging with AMQP protocol using Apache QPid Client.

 

CXF

camel-quarkus-cxf-soap

Expose SOAP WebServices using Apache CXF or connect to external WebServices using CXF WS client.

 

JDBC

camel-quarkus-jdbc

Access databases through SQL and JDBC.

 

SNMP

camel-quarkus-snmp

Receive traps and poll SNMP (Simple Network Management Protocol) capable devices.

SNMP version 3 is supported only for the operation poll. (This limitation is caused by an issue in Camel 3.18.6. For more information, see CAMEL-19298).

Vert.x HTTP Client

camel-quarkus-vertx-http

Camel HTTP client support with Vert.x.

 

YAML-DSL

camel-quarkus-yaml-dsl

A YAML stack for parsing YAML route definitions.

 

XML IO DSL

camel-quarkus-xml-io-dsl

An XML stack for parsing XML route definitions

 

1.10. Data formats added in this release

No data formats have been added in the version Camel Extensions for Quarkus release of 2.13.3.

1.11. Additional resources

Legal Notice

Copyright © 2023 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.