Solace JMS API

The messaging API for JMS uses the standard JMS interface to provide JMS service for Java-based applications through a Solace message router. The Solace JMS API supports JMS version 1.1.

To use the Solace JMS implementation in a Java Platform, Enterprise Edition (Java EE) application server environment, you can deploy a Solace‑provided, Java Connector Architecture (JCA) 1.5-compliant resource adapter for the particular Application Server platform being used to provide enterprise applications with connectivity to Solace routers. Solace currently provides a Resource Adapter for Red Hat JBoss EAP 6.2 and WebSphere Application Server V7 and V8. For more information, refer to Using Solace JMS in JEE Environments.

Note:  Solace JMS API has implemented a semantic versioning system that uses a numbering pattern of MAJOR.MINOR.PATCH. With this system, increments to each of these numbers has specific meanning:

  • MAJOR—incompatible API changes were made
  • MINOR—backwards-compatible functionality was added
  • PACH—backwards-compatible bug fixes were made
  • The last release prior to the implementation of the semantic version numbering was Version 7.2.2.

Message Exchange Patterns

The JMS API supports all common message exchange patterns.

  • Publish / Subscribe
  • Point to Point
  • Request / Reply

Features

The JMS API supports the following common API features.

  • Connection management to Solace message routers
  • Addition and removal of topic subscriptions
  • Sending and receiving messages Direct and Guaranteed messages
  • Structured data types that do not rely on a specific architecture or programming language
  • Extensive support for logging and customizing through property parameters
  • Request/reply messaging support
  • Session Transactions XA Transactions
  • Queue browsing
  • Topic dispatch
  • Maven support