1.2. Important Notes

Oracle JDK 1.7 is incompatible with Maven central repository

Due to recent changes in the security requirements for connecting to the Maven central repository, Oracle JDK 1.7 is no longer compatible with Maven central and is unable to download Maven artifacts. We recommend that you upgrade to Oracle JDK 1.8 to avoid this issue. See Section 4.2, “List of Known Issues” for more details.

New Maven repository

Since JBoss Fuse 6.3, the JBoss Fuse Maven artifacts are available only from the following Maven repositories:
Hence for JBoss Fuse 6.3, you need to edit your Maven settings.xml file, replacing the old repo.fusesource.com repository URLs (at https://repo.fusesource.com/nexus/content/repositories/releases and https://repo.fusesource.com/nexus/content/groups/ea) with the new Maven repository URLs.
Older versions of JBoss Fuse (prior to 6.3) continue to use the old Maven repositories.

ActiveMQ runtime can now be wired to JMS 2.0 API bundle in OSGi

In JBoss Fuse 6.3, the ActiveMQ runtime has been modified so that it is compatible with and can be wired to the JMS 2.0 API bundle. This does not imply that ActiveMQ supports JMS 2.0. In fact, ActiveMQ still supports JMS 1.1 only. This change does mean, however, that it is now possible to deploy an ActiveMQ broker (which is a JMS 1.1 application) alongside a JMS 2.0 compliant application in the same OSGi container. This can be useful, for example, if you want to deploy two different messaging products in the same Apache Karaf container.

Upgraded Jetty from 8.1.x to 9

In the Apache Karaf container, Jetty (which provides the default HTTP servlet container for Karaf) has been upgraded from Jetty 8.1.x to Jetty 9. This has a significant impact on the Jetty container configuration, affecting settings in the etc/org.ops4j.pax.web.cfg file, in the etc/jetty.xml file, and in the Camel Jetty endpoint. For more details, see chapter "Securing the Jetty HTTP Server" in "Security Guide" and chapter "Securing the Camel Jetty Component" in "Security Guide".

Apache Karaf package name changed from jboss-fuse-full to jboss-fuse-karaf

The package name for the Apache Karaf distribution of JBoss Fuse has changed from jboss-fuse-full-ProductVersion.zip to jboss-fuse-karaf-ProductVersion.zip in this release.

CXF security changes

Note the following important changes to CXF security in this release:
  • The STS (Security Token Service) now issues tokens using the RSA-SHA256 signature algorithm by default (previously RSA-SHA1), and the SHA-256 digest algorithm (previously SHA-1).
  • The SAML/XACML functionality previously available in the cxf-rt-security module is now in the cxf-rt-security-saml module.

New interceptor required for transactional RFC SAP endpoints

A new interceptor object is provided in JBoss Fuse 6.3, which is needed to configure transactional RFC destinations properly for the Camel SAP component. For details, see section "Interceptor for tRFC and qRFC destinations" in "Apache Camel Component Reference".

Make Quickstart Examples Available

In previous releases, profiles for quickstart example were available by default. The new default behavior is that profiles for quickstart examples are not available in a new fabric. To create a fabric in which you can run the quickstart examples, edit the $FUSE_HOME/fabric/io.fabric8.import.profiles.properties file by uncommenting the line that starts with the following:
# importProfileURLs =
If you create a fabric without doing this and you want to run the quickstart examples, follow these steps to make them available:
  1. Edit the $FUSE_HOME/quickstarts/pom.xml file to add a fabric I/O plugin, for example:
  2. In the $FUSE_HOME/quickstarts directory, change to the directory for the quickstart example you want to run, for example:
    cd beginner
  3. In that directory, execute the following command:
    mvn fabric8:deploy
    You would need to run this command in each directory that contains a quickstart example that you want to run.