Show Table of Contents
1.3. Important Notes
New Maven repository
Since JBoss A-MQ 6.3, the JBoss A-MQ Maven artifacts are available only from the following Maven repositories:
Hence for JBoss A-MQ 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.
Note
Older versions of JBoss A-MQ (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 A-MQ 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 and in the etc/jetty.xml file. For more details, see chapter "Securing the Jetty HTTP Server" in "Security Guide".
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.