1.15.0.RC1

Changes between 1.14.0 and 1.15.0.RC1

This is a release candidate for 1.14.0, a maintenance release that includes a new feature and dependency upgrades. It is backward-compatible with 1.13.0. All users are encouraged to experiment with this pre-release or even better, test 2.1.0.RC1, as 1.x general support period ends on 31 July 2020.

Thanks to @sdurrenmatt for his contribution on this pre-release.

Add channelsQos property to JNDI Factory

GitHub PR: #124

Bump dependencies

GitHub issue: #125

2.0.0

Changes between 1.x.x and 2.0.0

This major release introduces a few breaking changes, but the core of the API (support of the JMS API 1.1) is unchanged. The major changes are a requirement on Java 8 or more and the internal use of the RabbitMQ AMQP Client 5.x.

When upgrading from 1.x to 2.x, application code might no longer compile when configuring RMQConnectionFactory (see below for details). Application code for "usual" operations such as publishing and consuming should still compile without any changes.

All users are encouraged to use or upgrade to this version, as it is now the production line before 1.x goes end-of-life in the next few months.

Breaking changes

Java 8 is Now Required

The client no longer supports JDK 6 and 7. JDK 8 is now required to both build and run (use) this library.

Because of the Java 8 requirement, this client only supports Android 7.0 or later.

RMQConnectionFactory

• setAmqpPropertiesCustomiser accepts a BiFunction<AMQP.BasicProperties.Builder, Message, AMQP.BasicProperties.Builder> instead of a AmqpPropertiesCustomiser.
• setAmqpConnectionFactoryPostProcessor accepts a Consumer<com.rabbitmq.client.ConnectionFactory> instead of AmqpConnectionFactoryPostProcessor.
• setHostnameVerifier(HostnameVerifier) is removed, as the JVM can perform hostname verification itself as of Java 7. Use setHostnameVerification(true) instead.

2.0.0.RC1

Changes between 1.x.x and 2.0.0.RC1

This is a pre-release for a major release. It introduces a few breaking changes, but the core of the API (support of the JMS API 1.1) is unchanged. The major changes are a requirement on Java 8 or more and the internal use of the RabbitMQ AMQP Client 5.x.

When upgrading from 1.x to 2.x, application code might no longer compile when configuring RMQConnectionFactory (see below for details). Application code for "usual" operations such as publishing and consuming should still compile without any changes.

Users are encouraged to experiment with this pre-release as 2.x is going to become the main production line before 1.x goes end-of-life in the next few months.

Breaking changes

Java 8 is Now Required

The client no longer supports JDK 6 and 7. JDK 8 is now required to both build and run (use) this library.

Because of the Java 8 requirement, this client only supports Android 7.0 or later.

RMQConnectionFactory

• setAmqpPropertiesCustomiser accepts a BiFunction<AMQP.BasicProperties.Builder, Message, AMQP.BasicProperties.Builder> instead of a AmqpPropertiesCustomiser.
• setAmqpConnectionFactoryPostProcessor accepts a Consumer<com.rabbitmq.client.ConnectionFactory> instead of AmqpConnectionFactoryPostProcessor.
• setHostnameVerifier(HostnameVerifier) is removed, as the JVM can perform hostname verification itself as of Java 7. Use setHostnameVerification(true) instead.

1.14.0

Changes between 1.13.0 and 1.14.0

This is a maintenance release that includes a new feature and a usability improvement. It is backward-compatible with 1.13.0. All users are encouraged to upgrade to this release.

Thanks to @SethPyle376 and @meaghek for their contribution on this release.

Messages can be nack-ed on transaction rollback

GitHub issue: #121

Expose queue declare arguments in RMQSession

GitHub issue: #120

1.14.0.RC1

Changes between 1.13.0 and 1.14.0.RC1

This is a release candidate for 1.14.0, a maintenance release that includes a new feature and a usability improvement. It is backward-compatible with 1.13.0. All users are encouraged to experiment with this pre-release.

Thanks to @SethPyle376 and @meaghek for their contribution on this pre-release.

Messages can be nack-ed on transaction rollback

GitHub issue: #121

Expose queue declare arguments in RMQSession

GitHub issue: #120

1.13.0

Changes between 1.12.0 and 1.13.0

This is a maintenance release that includes a new feature, bug fixes and an upgrade of the RabbitMQ Java client dependency. It is backward-compatible with 1.12.0. All users are encouraged to upgrade to this release.

Add support for publisher confirms

GitHub issue: #115

Make sure RMQConnectionFactory is serializable

GitHub issue: #109

Add declareReplyToDestination flag to RMQObjectFactory

GitHub issue: #117

Bump Java client to 4.11.3

GitHub issue: #118

1.13.0.RC1

Changes between 1.12.0 and 1.13.0.RC1

This is a release candidate for 1.13.0, a maintenance release that includes a new feature, bug fixes and an upgrade of the RabbitMQ Java client dependency. It is backward-compatible with 1.12.0. All users are encouraged to experiment with this pre-release.

Add support for publisher confirms

GitHub issue: #115

Make sure RMQConnectionFactory is serializable

GitHub issue: #109

Add declareReplyToDestination flag to RMQObjectFactory

GitHub issue: #117

Bump Java client to 4.11.3

GitHub issue: #118

1.12.0

Changes between 1.11.2 and 1.12.0

This is a maintenance release that includes a bug fix and an upgrade of the RabbitMQ Java client dependency. This release is backward-compatible with 1.11.2. All users are encouraged to upgrade to this version.

JMSExpiration should be zero for non-expiring messages

GitHub issue: #112

Bump Java client to 4.11.2

GitHub issue: #114

1.12.0.RC1

Changes between 1.11.2 and 1.12.0.RC1

This is a release candidate for 1.12.0, a maintenance release that includes a bug fix and an upgrade of the RabbitMQ Java client dependency. This release is backward-compatible with 1.11.2.

JMSExpiration should be zero for non-expiring messages

GitHub issue: #112

Bump Java client to 4.11.2

GitHub issue: #114

1.11.2

Changes between 1.11.1 and 1.11.2

This is a patch release that includes a bug fix. This release is backward-compatible with 1.11.1. All users are encouraged to upgrade to this version.

Thanks to @welsh for their contribution on this release.

Avoid invalid warning when SSLContext is set

GitHub issue: #74