2.3. October 2016 GA

In the next major release of JBoss Fuse (planned as JBoss Fuse 7.0), Fabric8 v1 will be replaced by Fuse Integration Services (FIS), which includes components of Fabric8 v2 technology. FIS provides a set of tools and Docker-formatted images that enable development, deployment, and management of integration microservices within OpenShift.

Although FIS has a different architecture, it fulfills the same provisioning, automation, central configuration and management requirements that Fabric8 v1 provides. For more information, please see Red Hat JBoss Fuse Integration Services 2.0 for OpenShift.

Please contact Fuse Support with any questions or concerns.

The bin/deletefabric8 script has been removed in this release.

The GAE components for Apache Camel are deprecated in JBoss Fuse 6.3 and will be removed from a future release of JBoss Fuse.

The Camel Netty component and the SwitchYard Camel Netty component are both deprecated in JBoss Fuse 6.3 and will be removed in a future release of JBoss Fuse. It is recommended that you use the Camel Netty4 component instead.

The Camel jBPM component (camel-jbpm) is deprecated in JBoss Fuse 6.3 and will be removed in a future release of JBoss Fuse.

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.

The Tanuki based wrapper scripts—generated using the wrapper:install Karaf console command—for installing JBoss Fuse as a service are deprecated since JBoss Fuse 6.3 and will be removed in a future release of JBoss Fuse. 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.

Since JBoss Fuse 6.3, the Smooks component for SwitchYard is deprecated and will be removed in a future release of JBoss Fuse.

BPEL (based on the Riftsaw project) is no longer being actively developed and will be removed from a future release of JBoss Fuse. If you are currently using BPEL, it is recommended that you consider migrating to the Red Hat JBoss BPM Suite (which is supported through the JBoss Fuse Integration Package).

The Design Time Governance component is deprecated since 6.2.1 and not included with the product.

Since JBoss Fuse 6.3, the Runtime Governance (RTGov) component is deprecated and will be removed in a future release of JBoss Fuse.

The SOA Repository Artifact Model and Protocol (S-RAMP) component is deprecated since 6.2.1 and will be removed from a future release.

The bin/patch script (bin\patch.bat on Windows O/S) is deprecated and will be removed in a future release.

Spring-DM (which integrates Spring XML with the OSGi service layer) is deprecated since 6.2.1 and you should use the Blueprint framework instead. Using Blueprint does not prevent you from using the Java libraries from the Spring framework: the latest version of Spring is compatible with Blueprint.

The Apache OpenJPA implementation of the Java Persistence API (JPA) is deprecated since 6.2.1. It is recommended that you use the Hibernate implementation instead.