JMS Support
Important Note for JMS Users: Transition to Jakarta JMS API in ReadyAPI
Starting in version 3.61.0, ReadyAPI transitions from the javax.jms namespace to the jakarta.jms namespace, following the industry-wide shift from Java EE to Jakarta EE.
This update ensures compatibility with modern JMS providers and aligns ReadyAPI with current standards.
API Namespace Update: ReadyAPI adopts the Jakarta JMS API (
jakarta.jms) instead of the legacy Javax JMS API (javax.jms). This includes updates to internal dependencies and import statements in the codebase.Library Update: ReadyAPI now uses the
jakarta.jms-apilibrary in place of thejavax.jms-apilibrary.
The transition may impact your current JMS configuration in the following ways:
Client Libraries: If your JMS provider still uses the
javax.jmsnamespace, those libraries may not work with ReadyAPI 3.61.0.Custom Scripts and Plugins: Any custom code that references
javax.jmsclasses needs to switch to thejakarta.jmsequivalents.
To prepare for the update, we recommend taking the following steps:
Check JMS Provider Compatibility: Confirm that your JMS provider supports the Jakarta JMS API. If it doesn't, refer to the provider’s documentation or support team for upgrade options.
Update Client Libraries: Download the latest client libraries that support the
jakarta.jmsnamespace from your JMS provider.Update Custom Code: Replace any
javax.jmsreferences in your scripts or plugins withjakarta.jms.Test Your Configurations: After making these changes, run tests in ReadyAPI to ensure everything functions correctly.
If you need assistance during the transition, contact our support team through the Product Support Portal.
Java Message Service is an API for exchanging messages between applications. ReadyAPI supports JMS messaging, so you can send and receive both text and binary messages.
To test JMS services, you need to do the following:
Configure a JMS provider. The following topics provide information on how to configure some popular JMS providers:
Establish a connection to the provider. In ReadyAPI, you can do it in the following ways:
Important
ReadyAPI does not support using HermesJMS as a JMS connector starting with version 3.1.
If you use an earlier version of ReadyAPI, we still strongly recommend that you connect using one of the methods above because HermesJMS is no longer maintained by its developer.
Then, you can send JMS requests. The preferred way of sending JMS requests in ReadyAPI is using a JMS Request. Besides that, you can:
Use a SOAP Request to send an attachment as TextMessage or BytesMessage to a JMS endpoint.
Use a REST Request to send an attachment as TextMessage or BytesMessage to a JMS endpoint.
Use an HTTP Request to send an attachment as TextMessage or BytesMessage to a JMS endpoint.
Also, you can emulate a JMS server by using the JMS virtual services.