Red Hat Summit Red Hat SummitSuporteConsoleDesenvolvedoresComeçar um testeContato

Este conteúdo não está disponível no idioma selecionado.

Chapter 2. Camel Extensions for Quarkus 2.13.2 release notes

2.1. Camel Extensions for Quarkus features
Copiar o link

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 of the important aspects of a Camel Extensions for Quarkus application can be set up programmatically with CDI (Contexts and Dependency Injection) or via 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.

2.2. Supported platforms, configurations, databases, and extensions
Copiar o link

2.3. Technology preview extensions
Copiar o link

Red Hat does not provide support for Technology Preview components provided with this release of Camel Extensions for Quarkus. 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

CXF is a new Technology Preview component that is provided with this release of Camel Extensions for Quarkus. The following features are excluded from Technology Preview support:

  • RESTful services
  • CORBA support
  • UDP Transport
  • WS-MetadataExchange
  • WS-Discovery

2.4. Known CXF issues
Copiar o link

CEQ-5348 WS-SecurityPolicy, WS-Trust
When you use WS-SecurityPolicy or WS-Trust with a Camel CXF consumer, for example from("cxf:…​"), the SOAP endpoint throws the following exception: 
SoapFault: BSP:R3227: A SECURITY_HEADER MUST NOT contain more than one TIMESTAMP
Copy to Clipboard Toggle word wrap

You can workaround this issue by deploying the SOAP endpoint using the same approach as the Quarkiverse CXF extension.

First, you require an implementation of your service endpoint interface (SEI) that forwards your message to a Camel route. For example, if your SEI is similar to the following: 

@WebService(targetNamespace = "https://quarkiverse.github.io/quarkiverse-docs/quarkus-cxf/ws-securitypolicy")
public interface WssSecurityPolicyHelloService {
    @WebMethod
    String sayHello(String name);
}
Copy to Clipboard Toggle word wrap

Then, you must configure the implementation of your SEI as follows: 

@WebService(portName = "EncryptSecurityServicePort", serviceName = "WssSecurityPolicyHelloService", targetNamespace = "https://quarkiverse.github.io/quarkiverse-docs/quarkus-cxf/ws-securitypolicy", endpointInterface = "org.apache.camel.quarkus.component.cxf.soap.securitypolicy.server.cxf.way.it.WssSecurityPolicyHelloService")
public class WssSecurityPolicyHelloServiceImpl implements WssSecurityPolicyHelloService {
    @Inject
    ProducerTemplate producerTemplate;

    public String sayHello(String name) {
        return producerTemplate.requestBody("direct:myDirectEndpoint", name, String.class);
    }
}
Copy to Clipboard Toggle word wrap

Next, in the application.properties file, you must configure the path that will serve the service. For example: 

quarkus.cxf.path=/soap
quarkus.cxf.endpoint."/security-policy-hello".implementor=org.apache.camel.quarkus.component.cxf.soap.securitypolicy.server.cxf.way.it.WssSecurityPolicyHelloServiceImpl
Copy to Clipboard Toggle word wrap

In this example, where your Camel route normally starts with from("cxf:bean:myCxfHelloEndpoint"), it now starts with from("direct:myDirectEndpoint").

CEQ-5286 MTOM Attachments: Unmarshalling Error when invoking a CXF service with an AWT Image parameter

If your Service Endpoint Interface (SEI) refers to java.awt.Image in any of its method signatures, then the endpoint throws an error similar to the following:

  • {{Unmarshalling Error: unexpected element (uri:"", local:"arg0"). Expected elements are (none) }}
  • Unmarshalling Error: unexpected element (uri:"https://quarkiverse.github.io/quarkiverse-docs/quarkus-cxf/test/mtom-awt", local:"data"). Expected elements are (none)

You can workaround this issue by wrapping java.awt.Image inside a request or response data object. For example, you can configure your SEI as follows: 

@WebService(name = "ImageService", targetNamespace = ImageService.NS)
@MTOM
public interface ImageService {
    public static final String NS = "https://quarkiverse.github.io/quarkiverse-docs/quarkus-cxf/test/mtom-awt";

    @WebMethod
    Image downloadImage(@WebParam(name = "name", targetNamespace = NS) String name);

    @WebMethod
    String uploadImage(String name, Image image);
}
Copy to Clipboard Toggle word wrap

To use this workaround, you should configure your SEI as follows: 

@WebService(name = "ImageService", targetNamespace = ImageService.NS)
@MTOM
public interface ImageService {
    public static final String NS = "https://quarkiverse.github.io/quarkiverse-docs/quarkus-cxf/test/mtom-awt";

    @WebMethod
    ImageData downloadImage(@WebParam(name = "name", targetNamespace = NS) String name);

    @WebMethod
    String uploadImage(ImageData image);
}

@XmlType(name = "imageData", namespace = "http://org.jboss.ws/xop/doclit")
public class ImageData {
    private Image data;
    private String name;

    public ImageData() {
    }

    public String getName() {
        return name;
    }

    public void setName(String name) {
        this.name = name;
    }

    public Image getData() {
        return data;
    }

    public void setData(Image data) {
        this.data = data;
    }
}
Copy to Clipboard Toggle word wrap
CEQ-4769 CXF clients that contain a class with postponed initialization in their method signatures cannot be compiled to native
When a client of Service Endpoint Interface (SEI) refers to java.awt.Image in any of its methods, the application cannot compile to native. There is no known workaround for this issue, but you can still use the affected clients in JVM mode.

2.5. Important notes
Copiar o link

Support for AdoptiumJDK
Camel Extensions for Quarkus version 2.13.2 introduces support for AdoptiumJDK 11 and AdoptiumJDK 17.
Camel upgraded from version 3.14.2 to version 3.18.3

Camel Extensions for Quarkus version 2.13.2 has been upgraded from Camel version 3.14.2 to Camel version 3.18.3. 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.2 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:

2.6. Resolved issues
Copiar o link

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.2.

Expand
Table 2.1. Resolved issues
IssueDescription

CEQ-4769

Camel MLLP: Allow the ability to set MIN_BUFFER_SIZE for SocketBuffer.

CEQ-4754

Camel REST: Request URL duplicated context path.

CEQ-833

JMS components connection pooling.

CEQ-799

Request to support Camel Quarkus JTA+JPA integration.

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

2.7. Extensions added in this release
Copiar o link

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

Expand
Table 2.2. Added extensions
ExtensionArtifactDescription

Browse

camel-quarkus-browse

Inspect the messages received on endpoints supporting BrowsableEndpoint.

CXF

camel-quarkus-cxf-soap

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

Dataformat

camel-quarkus-dataformat

Use a Camel Data Format as a regular Camel Component.

Google BigQuery

camel-quarkus-google-bigquery

Access Google Cloud BigQuery service using SQL queries or Google Client Services API.

Google Pubsub

camel-quarkus-google-pubsub

Send and receive messages to/from Google Cloud Platform PubSub Service.

Kubernetes

camel-quarkus-kubernetes

Perform operations against Kubernetes API.

REST OpenApi

camel-quarkus-rest-openapi

Configure REST producers based on an OpenAPI specification document delegating to a component implementing the RestProducerFactory interface.

2.8. Data formats added in this release
Copiar o link

The following table lists the data formats that have been added in this release of Camel Extensions for Quarkus version 2.13.2.

Expand
Table 2.3. Added data formats
ExtensionArtifactDescription

JAXB

camel-quarkus-jaxb

Unmarshal XML payloads to POJOs and back using JAXB2 XML marshalling standard.

Voltar ao topo
Red Hat logoGithubredditYoutubeTwitter

Aprender

Experimente, compre e venda

Comunidades

Sobre a documentação da Red Hat

Ajudamos os usuários da Red Hat a inovar e atingir seus objetivos com nossos produtos e serviços com conteúdo em que podem confiar. Explore nossas atualizações recentes.

Tornando o open source mais inclusivo

A Red Hat está comprometida em substituir a linguagem problemática em nosso código, documentação e propriedades da web. Para mais detalhes veja o Blog da Red Hat.

Sobre a Red Hat

Fornecemos soluções robustas que facilitam o trabalho das empresas em plataformas e ambientes, desde o data center principal até a borda da rede.

Theme

© 2025 Red Hat