The API now supports TLS 1.3. This feature requires an Event Broker that also supports TLS 1.3.

Enables adding and extracting tracing metadata attached to events published and received by the Solace Java API.

The Java API now supports end-to-end payload compression. Sessions can now be optionally configured to compress the payload of every message on a message-by-message basis. While enabling this feature severely impacts API performance for small messages and significantly impacts API performance for larger messages, it has a positive impact on Event Broker performance and message-spool usage.

The Java API now supports the WebSocket transport protocol.

We have simplified the API license text and clarified that distributing works containing the Solace APIs is allowed.

The API now supports connecting to a Solace broker via an HTTP or SOCKS5 proxy.

The Messaging API for Java now supports message NACK.

This enhancement adds support for Partitioned Queues to the API. Partitioned Queues expand PubSub+ to provide deterministic, ordered, and non-exclusive message delivery for customers to scale the number of consumers when publishing ordered datasets. The ordered datasets are keyed to ensure all events in the dataset are sent to the same consumer without mis-ordering events.

This enhancement provides a browser interface that allows applications to look at Guaranteed Messages spooled for a queue in the order of oldest to newest without consuming them.

The API now supports synchronous request/reply with helper classes to await response from a replier.

OAuth / OpenID Connect has been added as a method of authenticating and authorizing clients connecting to the PubSub+ Event Broker using the SMF protocol. Clients using Solace APIs will be able to present a token as a credential during client login. This enables clients to integrate with modern identity and access management systems.

This feature compares the DNS name that the API is trying to connect to with the DNS name stored in the subject alternate name of the server certificate, following the current security best practice for TLS connections.

This is the initial release of the PubSub+ Messaging API for Java. Solace created this API to modernize our JCSMP API. This is a separate standalone API which provides modern interfaces, patterns, and usability in a native Java environment.

This version contains a feature set that allows for common messaging patterns like publish/subscribe using Direct Messaging and Guaranteed Messaging. This API provides support for all deployments of PubSub+ across software, appliance, and cloud.

Future versions of the Java API will introduce more features as Solace builds out the roadmap for this API.

The Java API 1.0.0 supports:

* Connection management to PubSub+ event brokers

* Addition and removal of topic subscriptions

* Sending and receiving Direct and Guaranteed Messages

* Message compression

* Use of Selectors

* Kerberos authentication

* Message Replay

* Structured data types that allow interoperability between various architectures and programming languages

The Java API 1.0.0 does not support the following features:

* Request/Reply message exchange pattern

* PubSub+ Cache Client API support

* Session Transactions

* XA Transactions

* Queue browsing

Applications can now replay messages following the message-ID of the last message which they successfully-processed.

The feature uses "replication group message ID", which uniquely identifies messages within an HA group and Replication/DR group of brokers. The broker includes this ID in all guaranteed messages it delivers to the consumer. Consuming applications can extract and save this ID along with the message payload, and then use it later to initiate a replay.

This is a more "fine-grained" way to start a replay than from date-and-time, and is ideal in cases where the last message-ID successfully processed is known by the application (e.g. recovery from a database crash).