Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 5. Deprecated and Removed Features

If you need any assistance or have any questions about the upcoming changes in Fuse 7, please contact support@redhat.com.

5.1. Technology Preview 4
Copy link

The following features have been deprecated or removed in JBoss Fuse 7.0-TP:

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. Customers should connect to a supported remote broker directly. For more information on our supported brokers, refer to the messaging lifecycle.
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.
JBoss 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.
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.
Karaf console commands for child container administration have been removed in 7.0
In JBoss Fuse 7.0, the Karaf console commands for child container administration (commands prefixed by admin:, such as admin:create, admin:list, and so on) have been removed.
SwitchYard has been removed in 7.0
In JBoss 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 JBoss Fuse 7.
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.

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, please 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 JBoss Fuse 7.0.
Camel Netty component is deprecated
The Camel Netty component is deprecated in JBoss Fuse 7.0 and will be removed in a future release of JBoss Fuse. It is recommended that you use the Camel Netty4 component instead.
Camel jBPM component has been removed in 7.0
The Camel jBPM component (camel-jbpm) has been removed in JBoss Fuse 7.0.
Camel LevelDB component is deprecated on all operating systems except for Linux
Since JBoss 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.
Tanuki based wrapper for installing JBoss Fuse as a service has been removed in 7.0
The Tanuki based wrapper scripts — generated using the wrapper:install Karaf console command — for installing JBoss Fuse as a service have been removed in JBoss Fuse 7.0. To install the Apache Karaf container as a service, it is recommended that you use the new karaf-service-*.sh scripts from the bin/contrib directory instead.
Smooks has been removed in 7.0
In JBoss 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 JBoss 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
In JBoss 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 JBoss Fuse 7.0.
bin/patch script has been removed in 7.0
The bin/patch script (bin\patch.bat on Windows O/S) has been removed in a JBoss 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 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.
Apache OpenJPA is not supported in 7.0
The Apache OpenJPA implementation of the Java Persistence API (JPA) is not supported in JBoss Fuse7.0. It is recommended that you use the Hibernate implementation instead.
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

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.

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

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

Theme

© 2026 Red HatBack to top