Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 4. JBoss Fuse Standalone

4.1. Supported containers
Copy link

JBoss Fuse standalone 7.0 TP4 is supported on the following runtime containers:

  • Spring Boot (standalone)
  • Apache Karaf
  • Red Hat JBoss Enterprise Application Platform (JBoss EAP)

4.2. New features
Copy link

The main new features of JBoss Fuse standalone in version 7.0 TP4 are:

  • Spring Boot standalone is now a deployment option for JBoss Fuse applications. Standalone mode is where a Spring Boot application is built as a Jar file and runs directly in a Java virtual machine (JVM).
  • Major upgrade of JBoss EAP to version 7.1.
  • Apache Camel is upgraded to version 2.21.

  • The following Apache Camel components are new in JBoss Fuse 7.0:

    • camel-atomix - a component to integrate Camel with Atomix
    • camel-aws - KMS component for managing Amazon KMS
    • camel-aws - MQ component for working with Amazon MQ
    • camel-aws - added lamda component to be used for invoking and working with AWS Lambda functions
    • camel-azure - to integrate with Microsoft Azure Cloud services
    • camel-caffeine - a component that allows you to interact with a Caffeine cache
    • camel-couchbase - The couchbase component allows you to treat CouchBase instances as a producer or consumer of messages.
    • camel-crypto-cms - a component for cryptographic message syntax
    • camel-digitalocean - The digitalocean component allows you to interact with the Digitalocean cloud
    • camel-drill - The drill component gives you the ability to querying to Apache Drill Cluster
    • camel-elasticsearch5 - to communicate with Elasticsearch Server using 5.x APIs
    • camel-elasticsearch-rest - The elasticsearch component is used for interfacing with ElasticSearch server using 5.x REST API.
    • camel-google-bigquery - Google BigQuery data warehouse for analytics (not on Apache Karaf).
    • camel-google-pubsub - allow you communicate with Google Cloud Pub/Sub
    • camel-grpc - The gRPC component is using for calling remote procedures via HTTP/2
    • camel-headersmap - a faster implementation of case-insenstive map (used by camel message headers) which can be added to classpath at runtime to be auto installed
    • camel-iec60870 - to integrate Camel with IEC 60870-5-104 IoT devices
    • camel-master - a component that leverage Cluster SPI to ensure that only a single consumer in a camel cluster is active at any point in time.
    • camel-milo - An OPC UA client and server component based on Eclipse Milo
    • camel-mongodb3 - Evolution of the component based on v3 driver. Camel-Mongodb still exists allowing compatibility with the v2 driver.
    • camel-olingo4 - Communicates with OData 4.0 services using Apache Olingo OData API.
    • camel-openstack - allow you to communicate with an Openstack infrastructure
    • camel-opentracing - Distributed tracing using OpenTracing
    • camel-pubnub - To send and receive messages to PubNub data stream network for connected devices.
    • camel-reactor - a reactor based back-end for camel’s reactive streams component
    • camel-rest-swagger - for accessing REST resources using Swagger specification as configuration
    • camel-sjms2 - JMS 2.0 api compatible component of the SJMS component.
    • camel-spring-cloud - integrates with Spring Cloud
    • camel-spring-cloud-netflix - integrates with Spring Cloud Netflix (not on Apache Karaf or JBoss EAP).
    • camel-thrift - the Thrift component allows to call and expose remote procedures (RPC) with Apache Thrift data format and serialization mechanism
    • camel-tika - integrates with Apache Tika to extract content and metadata from thousands of file types
    • camel-twilio - a component that allows you to interact with Twilio REST APIs to call phones, send texts, etc. from a Camel route
    • camel-wordpress - To integrate Camel with Wordpress (not on JBoss EAP).
    • camel-xchange - The camel-xchange component provide access to many bitcoin and altcoin exchanges for trading and accessing market data (not on JBoss EAP).
    • camel-yql - The YQL (Yahoo! Query Language) platform enables you to query, filter, and combine data across the web (not on JBoss EAP).
    • camel-zendesk - interacts with Zendesk server with using Zendesk Java Client

  • Apache Camel features the following new Enterprise Integration Patterns:

    • Claim Check EIP with push/pop functionality.
    • Saga EIP for simulating transactions in distributed systems.

  • Apache Camel supports the following new data formats:

    • camel-asn1 - the ASN.1 data format is used for file transfer with telecommunications protocols.
    • camel-fastjson - JSon data format (using the FastJSon library) is used to unmarshal a JSon payload to a POJO; or to marshal a POJO back to a JSon payload.
    • camel-thrift - the Thrift data format allows you to call and expose remote procedure calls (RPC) with the Apache Thrift data format and serialization mechanism.
  • Many more Camel components are available for Camel on JBoss EAP. There are now almost as many Camel components available for the JBoss EAP container as for the Apache Karaf container.
  • Major upgrade of Apache Karaf, from version 2.4 to version 4.x.
  • Apache Karaf supports OSGi R6 (upgraded from OSGi R5).
  • Apache Karaf is now configured to use the Narayana transaction manager (replacing the Geronimo transaction manager used in JBoss Fuse 6.x).
  • Apache Karaf now supports the Undertow servlet container.
  • Apache Karaf has a new features resolver, which simplifies feature installation and lifecycle. The new resolver checks the feature requirements (defined directly in the features XML), and checks which bundles provide the capabilities to satisfy those requirements. It enables Karaf to install bundles required by features automatically.

  • Client-side integration with AMQ 7 (based on ActiveMQ Artemis) is supported in JBoss Fuse 7.0.

    • To access the Artemis JMS client from the Apache Karaf container in this technology preview, install the artemis-core feature.
    • To connect to an Artemis broker from the JBoss EAP container, use the embedded Artemis 1.5 resource adapter, which comes with JBoss EAP 7.1.
    • To access the Artemis JMS client from the Spring Boot container in this technology preview, use the artemis-jms-client Maven dependency with version 2.4.0.amq-710008-redhat-1.
  • Web tooling has been upgraded to the PatternFly look and feel.

4.3. Important notes
Copy link

Important notes for the JBoss Fuse 7.0 TP4 release of the JBoss Fuse standalone distribution:

Support for Fabric8 1.x has been removed in 7.0
In JBoss 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.
SwitchYard has been removed in 7.0
In JBoss Fuse 7.0, SwitchYard has been removed, and you should use Apache Camel directly instead.
Embedded ActiveMQ broker has been removed in 7.0
In JBoss Fuse 7.0, JBoss Fuse on Karaf no longer provides an embedded ActiveMQ Broker. Instead of using an embedded broker, you can connect to a supported remote broker.
Spring Dynamic Modules (Spring-DM) is not supported Apache Karaf in 7.0
Spring-DM (which integrates Spring XML with the OSGi service layer in Apache Karaf) is not supported in JBoss 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.
Jetty container has been replaced in 7.0
In JBoss 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 will be removed in a future release.
Geronimo transaction manager has been replaced in 7.0
In JBoss Fuse 7.0, the Geronimo transaction manager in the Karaf container has been replaced by Narayana.
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.
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Legal Notice

Theme

© 2026 Red HatBack to top