Chapter 2. Deprecated and Removed Features

In the next major release of JBoss A-MQ (JBoss A-MQ 7.0), support for most of the OpenWire clients will be dropped. The only OpenWire client that will continue to be supported is OpenWire JMS.

In the next major release of JBoss A-MQ (JBoss A-MQ 7.0), both the KahaDB message store and the LevelDB message store will be dropped. JBoss AMQ 7 has its own message store implementation and data model.

While JBoss AMQ 7 will support a JDBC adapter, the JBoss A-MQ 6.x JBDC adapter will not be supported on JBoss AMQ 7. A new JDBC store will need to be created.

In the next major release of JBoss A-MQ (JBoss A-MQ 7.0), the Apache Karaf (OSGi) container will be dropped. JBoss A-MQ 7.0 will be packaged as a standalone application, without any container technology.

In the next major release of JBoss A-MQ (planned as JBoss A-MQ 7.0), Fabric8 version 1 will be dropped, to be replaced by Fabric8 version 2. The Fabric8 version 2 upgrade is a new generation of distributed container technology that is entirely cloud-based and leverages the OpenShift technology stack to provide the foundation for containerized JBoss A-MQ applications.

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

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

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.

REST API is not supported in JBoss A-MQ 6.x and never has been. The REST API described in the Apache ActiveMQ community documentation, http://activemq.apache.org/rest.html, is only a demonstration, not a fully-developed feature. It cannot be used with JBoss A-MQ 6.x and has multiple gaps in its functionality that make it unsuitable for production use.