rabbitmq-jms-client
rabbitmq-jms-client copied to clipboard
rabbitmq
RabbitMQ JMS client
Right now the conversion from the native AMQP message to a JMS message is hardcoded, which is not great for interoperability. JMS "AMQP" destinations provide some interoperability, but are limited...
https://github.com/rabbitmq/rabbitmq-jms-client/issues/176 switches to `javax.jms:jms` from geronimo specs. There is a problem with migrating to javax.jms; there's no jar associated with the POM file in mavenCentral which has caused problems for...
# Background RabbitMQ JMS Client 2.x supports JMS 1.1 API, it requires Java 8. This is the current version of the library. JMS 2.0 introduces [API changes](https://www.oracle.com/technical-resources/articles/java/jms20.html) and some [new...
To reproduce: Unpack and build the attached archive. On one command-line start the server: ` java -cp example-1.0-shaded.jar JMSPassiveRpcServerTest` On a second command-line run the client: ` java -cp example-1.0-shaded.jar...
See https://github.com/rabbitmq/rabbitmq-jms-client/issues/109 for background. We only have a hypothesis there but it's a good problem to be proactive about: given that JNDI can serialise key classes from this client, we...
Update just the dependency and throw UnsupportedOperationExceptions for each JMS 2.0 methods. References #180
[JMS 3.1 Spec "A.3.16. Subscription name characters and length"](https://jakarta.ee/specifications/messaging/3.1/jakarta-messaging-spec-3.1.html#subscription-name-characters-and-length-2) The validation can be enabled with a flag, it's disabled by default, to avoid breaking existing code. The flag is `RMQConnectionFactory#validateSubscriptionNames`.